FreeRTOS-Kernel/FreeRTOS
Paul Bartell 7a695784bc
Add queue.c CMock unit test (#552)
* Disregard coverage data without a function_name field set

* Fix calling make on subdirectories

* Undefine FORTIFY_SOURCE when running without ENABLE_SANITIZERS

* Add queue and semaphore unit tests

* Update FreeRTOS-Kernel submodule revision
2021-04-20 15:45:52 -07:00
..
Demo Revert "Add test for timer start delayed past expiration (#557)" (#566) 2021-04-17 15:50:15 -07:00
License Update version number in readiness for V10.3.0 release. Sync SVN with reviewed release candidate. 2020-02-07 20:14:50 +00:00
Source@71f5af4e0f Add queue.c CMock unit test (#552) 2021-04-20 15:45:52 -07:00
Test Add queue.c CMock unit test (#552) 2021-04-20 15:45:52 -07:00
links_to_doc_pages_for_the_demo_projects.url Microblaze: Add a port optimised task selection implementation to the Microblaze port. 2015-06-24 15:10:03 +00:00
README.md Updated README in FreeRTOS/FreeRTOS (#317) 2020-10-27 00:02:56 -07:00

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.

See also -