* All for the Demo/Cortex_MPU_Simulator_Keil_GCC GCC demo: + Update the linker script so the project builds now the heap is part of the privileged data. + Add simulator.ini to setup the simulator memory map when the debugger starts to prevent invalid access errors. + Set configENFORCE_SYSTEM_CALLS_FROM_KERNEL_ONLY to 1 in FreeRTOSConfig.h, then fix up resultant build errors. + Set configALLOW_UNPRIVILEGED_CRITICAL_SECTIONS to 0 in FreeRTOSConfig.h, then fix up resultant build errors. * Fix compiler warning in Arm startup file. * Update comments in the file headers to pass the git checkin tests. * Update header comments to pass git checkin tests. * Second attempt to get file header comments correct for the check-in tests. * Third attempt to get the header comments correct. * Fix spelling. * Fix manifest check Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> Co-authored-by: none <> Co-authored-by: Gaurav Aggarwal <aggarg@amazon.com> |
||
---|---|---|
.. | ||
Demo | ||
License | ||
Source@356fff8028 | ||
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.