* Update kernel and community-supported-demos submodule pointer to apply compile option change on RP2040 * Update manifest * Update +TCP submodule pointer * Revert "Update +TCP submodule pointer" This reverts commit d090230eef40f26a2a2c9b5f3d2d1b7a043a7521. --------- Co-authored-by: kar-rahul-aws <118818625+kar-rahul-aws@users.noreply.github.com> Co-authored-by: chinglee-iot <61685396+chinglee-iot@users.noreply.github.com> |
||
---|---|---|
.. | ||
Demo | ||
License | ||
Source@7372519cba | ||
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.