FreeRTOS-Kernel/FreeRTOS
RichardBarry 6a8e2ba7dc
The zc702 Configuration QEMU.launch file contained an absolute path. This commit makes it project relative. (#761)
Co-authored-by: none <>
Co-authored-by: Rahul Kar <118818625+kar-rahul-aws@users.noreply.github.com>
2024-02-17 00:23:12 +05:30
..
Demo The zc702 Configuration QEMU.launch file contained an absolute path. This commit makes it project relative. (#761) 2024-02-17 00:23:12 +05:30
License
Source@7284d84dc8
Test Add SMP schedule equal priority on target test (#1170) 2024-02-08 11:07:39 +05:30
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.

See also -