27cbc7f6a2
* Update M33F simulator Keil example The example is updated to use latest CMSIS 5.9.0 and Device startup 2.1.0. Signed-off-by: Devaraj Ranganna <devaraj.ranganna@arm.com> * Increase timeout and correct config file path in the secure project Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> * Remove auto-generated files Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> --------- Signed-off-by: Devaraj Ranganna <devaraj.ranganna@arm.com> Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> Co-authored-by: Gaurav Aggarwal <aggarg@amazon.com> Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@1b8a4244bd | ||
| 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.