* Introduce tasks that test the coherency of the reported space available in a message buffer from two separate tasks. Designed to highlight the issue reported in https://github.com/FreeRTOS/FreeRTOS-Kernel/pull/264 Introduce configRUN_ADDITIONAL_TESTS which must be set to 1 to run the new tests. That is because the new tests got added to an existing standard demo file and smaller platforms may not have the resources to run them. Set configRUN_ADDITIONAL_TESTS to 1 in the MSVC and IAR/QEMU project so both project run the new test. Also add missing 'volatile' qualifier in the IAR/QEMU project on some register accesses. * Update xAreMessageBufferTasksStillRunning() to report errors from the new message buffer size coherency tests. Co-authored-by: RichardBarry <ribarry@amazon.com> Co-authored-by: RichardBarry <3073890+RichardBarry@users.noreply.github.com> |
||
---|---|---|
.. | ||
Demo | ||
License | ||
Source@23f641850d | ||
Test | ||
History.txt | ||
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.