Richard Barry

If that issue the issue, then it will be caught by defining configASSERT in most FreeRTOS architecture ports. Rationale for separate API is here: https://freertos.org/FAQ_API.html#IQRAPI

If that issue the issue, then it will be caught by defining https://freertos.org/a00110.html#configASSERT in most FreeRTOS architecture ports. Rationale for separate API is here: https://freertos.org/FAQ_API.html#IQRAPI

If you are not deliberateily using the MPU then it might be the build system has automatically picked up the mpu files unnecessarily. As per the above, that can get sorted on the FreeRTOS forums. 10 times bigger Presumably an exageration. duplication of the APIs now spills over to the QP port, so you have stuff like Q_NEW_FROM_ISR(), etc. Can't you keep the single API, then test to see if you are in an interrupt within that API's implementation, then call the appropriate FreeRTOS API once you know...

Unfortunately, there are currently no examples for the Keil uVision, because FreeRTOS has no official port to the ARM Compiler-6. (They only have ports for the outdated ARM Compiler-5). Many people create FreeRTOS project directly from within uVision, and from CMSIS packs. If you use Arm compiler V5 then use the FreeRTOS port files from the FreeRTOS/Source/Portable/RVDS directory of the kernel distribution. If you use Arm compiler V6 then use the FreeRTOS port files from the FreeRTOS/Source/Portable/GCC...

There is a sign up button and a sign in button on the top right of the forum page. You can sign in with a github account if you don't want to create a forum account.

endless loops on vPortRaiseBASEPRI on disassembly

The assembly code bares no resemblance to the source code, especially as the source function is written in assembly. For that reason I am confident this is not a FreeRTOS bug. Please create a support request on https://forums.freertos.org and we can help diagnose for you. Additionally, SourceForge is no longer our primary repository. Please see https://github.com/freertos

Compiler Warnings Generated with Keil C166 EC++ Compiler