FreeRTOS-Kernel/FreeRTOS
Kareem Khazem c7b3124565
Use CBMC XML output to enable VSCode debugger (#912)
Prior to this commit, CBMC would emit logging information in plain text
format, which does not contain information required for the CBMC VSCode
debugger. This commit makes CBMC use XML instead of plain text.

Co-authored-by: Mark Tuttle <tuttle@acm.org>
2023-01-13 13:03:06 -08:00
..
Demo CI: add win32-mingw demo to GithubActions workflow 2022-12-21 13:09:02 -08: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@bb6071e1df Update kernel submodule pointer for equal priority test cases (#909) 2023-01-09 18:05:20 +08:00
Test Use CBMC XML output to enable VSCode debugger (#912) 2023-01-13 13:03:06 -08: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 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 -