4f87f485d5
* Undo syntax changes preventing VeriFast parsing * Update proofs inline with source changes Outstanding: - xQueueGenericReset return code - Not using prvIncrementQueueTxLock or prvIncrementQueueRxLock macros * Remove git hash check * Document new changes between proven code and implementation * Update copyright header * VeriFast proofs: turn off uncrustify checks Uncrustify requires formatting of comments that is at odds with VeriFast's proof annotations, which are contained within comments. * Update ci.yml Co-authored-by: Joseph Julicher <jjulicher@mac.com> Co-authored-by: Aniruddha Kanhere <60444055+AniruddhaKanhere@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@b0a8bd8f28 | ||
| Test | ||
| links_to_doc_pages_for_the_demo_projects.url | ||
| README.md | ||
Directories:
-
The FreeRTOS/Source directory contains the FreeRTOS source code, and contains its own readme file.
-
The FreeRTOS/Demo directory contains a demo application for every official FreeRTOS port, and contains its own readme file.
-
The FreeRTOS/Test directory contains the tests performed on common code and the portable layer code, and contains its own readme file.
See FreeRTOS/SourceOrganization for full details of the directory structure and information on locating the files you require.
The easiest way to use FreeRTOS is to start with one of the pre-configured demo application projects (found in the FreeRTOS/Demo directory). That way you will have the correct FreeRTOS source files included, and the correct include paths configured. Once a demo application is building and executing you can remove the demo application file, and start to add in your own application source files.