You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
IotTaskPool_CreateSystemTaskPool() calls synchronisation primitives, so cannot be called before the scheduler starts. Add a configASSERT() to ensure the scheduler is running when it executes. IotTaskPool_CreateSystemTaskPool() can conceivably be called from multiple different libraries that depend on the thread pool. In this version _IotSystemTaskPool.running can be used to check the system task pool has not already been created. If the task pool has been created simply return from IotTaskPool_CreateSystemTaskPool() instead of re-creating it (which would leak memory and leave orphaned tasks). Call taskENTER_CRITICAL() and taskEXIT_CRITICAL() directly in place of mapping them to TASKPOOL_ENTER_CRITICAL() and TASKPOOL_EXIT_CRITICAL() in the same file. Rename _timerThread() _timerCallback(), as it is a callback function and not a thread. Remove the unused flags parameter from _scheduleInternal(). |
6 years ago | |
---|---|---|
FreeRTOS | 6 years ago | |
FreeRTOS-Plus | 6 years ago | |
FreeRTOS+TCP.url | 6 years ago | |
New - Stream and Message Buffers.url | 7 years ago | |
Quick_Start_Guide.url | 12 years ago | |
Upgrading-to-FreeRTOS-9.url | 9 years ago | |
Upgrading-to-FreeRTOS-10.url | 7 years ago | |
readme.txt | 12 years ago |
readme.txt
Directories: + FreeRTOS/source contains the FreeRTOS real time kernel source code. + FreeRTOS/demo contains a pre-configured demo project for every official FreeRTOS port. + See http://www.freertos.org/a00017.html for full details of the FreeRTOS directory structure and information on locating the files you require. + FreeRTOS-Plus contains additional FreeRTOS components and third party complementary products. THESE ARE LICENSED SEPARATELY FROM FreeRTOS although all contain open source options. See the license files in each respective directory for information. + FreeRTOS-Plus/Demo contains pre-configured demo projects for the FreeRTOS-Plus components. Most demo projects run in a Windows environment using the FreeRTOS windows simulator. These are documented on the FreeRTOS web site http://www.FreeRTOS.org/plus Further readme files are contains in sub-directories as appropriate. 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