FreeRTOS-Kernel/FreeRTOS
RichardBarry 2808e48079
Fix compiler warning in MessageBufferDemo.c (#842)
* prvReceiverTask() in MessageBufferDemo.c declared a variable as a "MessageBufferHandle_t *" instead of just a "MessageBuffer_t".  This came to light when updating the kernel submodule pointer as the underlying datatype changed in the kernel from a void *.

* Remove additional line that was preventing automated uncrustify tests from passing.

Co-authored-by: none <>
2022-08-18 10:41:39 +05:30
..
Demo Fix compiler warning in MessageBufferDemo.c (#842) 2022-08-18 10:41:39 +05:30
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@b0a8bd8f28 Upgrade kernel submodule version (#840) 2022-08-10 15:40:46 -07:00
Test Kernel timers.c tasks.c Unit Test (#539) 2022-08-16 14:38:26 -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 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 -