FreeRTOS-Kernel/FreeRTOS
Tony Josi a3a526569f
Enable release from forks (#1299)
* Enable release from forks

* Update Kernel submodule pointer

* Update manifest file

---------

Co-authored-by: Rahul Kar <karahulx@amazon.com>
2024-11-19 15:19:14 +05:30
..
Demo Add volatile qualifier (#1283) 2024-10-17 11:08:16 +05:30
License Use CI-CD-Github-Actions for spelling and formatting, add in the bot formatting action, update the CI-CD workflow files. Fix incorrect spelling and formatting on files. (#1083) 2023-09-06 12:35:37 -07:00
Source@7e419c2dd5 Enable release from forks (#1299) 2024-11-19 15:19:14 +05:30
Test Don't expect call to xTaskResumeAll in some cases (#1295) 2024-11-12 12:31:58 +05:30
links_to_doc_pages_for_the_demo_projects.url Use CI-CD-Github-Actions for spelling and formatting, add in the bot formatting action, update the CI-CD workflow files. Fix incorrect spelling and formatting on files. (#1083) 2023-09-06 12:35:37 -07:00
README.md Add uncrustify github workflow (#659) 2021-07-22 14:23:48 -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 -