mirror of
https://github.com/FreeRTOS/FreeRTOS-Kernel.git
synced 2025-04-19 21:11:57 -04:00
16639d2d63
Improve commenting in RISC-V GCC port. Fix IAR RISC-V port so the first task starts with interrupts enabled. Add references to third party page ref using newlib with FreeRTOS into the tasks.c file in each place newlib is referenced. Move the position of the traceTASK_DELETE() trace macro in case of use with a memory allocator that writes over freed memory even when inside a critical section. Efficiency improvement: Make sure xTaskIncrementTick() does not return pdTRUE when the scheduler is locked. This just prevents an unnecessary yield interrupt (unnecessary as it is ignored) when xYieldPending happens to be pdTRUE. |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source | ||
| History.txt | ||
| links_to_doc_pages_for_the_demo_projects.url | ||
| readme.txt | ||
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. + See http://www.freertos.org/a00017.html 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 - http://www.freertos.org/FreeRTOS-quick-start-guide.html http://www.freertos.org/FAQHelp.html