FreeRTOS-Kernel/FreeRTOS
chinglee-iot 6518cb153d
Update cellular comm interface to generate interrupt from windows thread (#1221)
* Make use of vPortGenerateSimulatedInterruptFromWindowsThread to generate interrupt from windows thread
2024-05-20 16:15:02 +08:00
..
Demo Demo/CORTEX_MPS2_QEMU_IAR_GCC cleanup (#1213) 2024-04-22 15:00:13 +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@29b202a41e Update cellular comm interface to generate interrupt from windows thread (#1221) 2024-05-20 16:15:02 +08:00
Test Fix vTaskSuspendAll assertion unit test (#1204) 2024-04-11 14:49:30 +08:00
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 -