FreeRTOS CMSIS V1 Works but not CMSIS V2

[kosh04]

I'm using a NUCLEO STM32F303K8 board attempting to use FreeRTOS, and I have a halting problem when I use CMSIS V2. I found this out by just trying to toggle the built-in LED using HAL using one statically allocated task and observing that the LED only toggles once.(I have OSdelay of 500, so I should be able to observe it). When I run into the debugger, it gets stuck in the default_handler. I then tried using CMSIS V1 and it toggles just fine. My question is is there any documentation on this? I've tried looking around, but haven't had any luck.  I've used FreeRTOS on other STM32's/NUCLEO boards and I haven't had a problem using CMSIS V2. Just to clarify, I don't mind using CMSIS V1. I was just wondering if others knew the problem or experienced the same issue.

[mbarg.1]

FreeRTOS is known to have several limitations and bugs - I strongly suggest to move to AZRTOS which is several oders of magnitude more stable and reliable. Don't waste your time with obsolete solution, move to code that you can use to deliver your product in shortest time & many will be happy to help you !

[ahsrabrifat]

Looks like the F3 series does not support CMSIS V2. https://community.st.com/t5/stm32-mcus-products/cmsis-version-for-cmsis-device-f3/td-p/630939

[KnarfB]

> FreeRTOS is known to have several limitations and bugs

do you have references for that claim?

hth

KnarfB

[mbarg.1]

Well, it is a long story ..

I (and many other) raised several claims years ago till 3 years ago when STM announced to focus on AZRTOS and drop FreeRTOS + Lwip support - and STM devoleper in a F2F meeting 2 years ago confirmed to me that they had no interest fixing bugs in FreeRTOS + LwIP.

It is also true that last year another STM official told me that they were re-dicussing this decision, but so far I did not see any anouncement on this topic.

I tested few monthes HTTP webserver example on H723 nucleo and still crash on a Syn flood test, one of the known bug.

Since then I suggest to newcomers to focus on AZRTOS + NetXDuo - and in my experience is much more reliable.

[MHoll.2]

So Your bad experience is not with FreeRTOS but with LwIP.
I'm using both FreeRTOS and ThreadX (AZRTOS was "donated" by Microsoft to the Eclipse Foundation and  renamed to it's original Name)..
In my opinion both kernals are equally stable, the problems starts when You add things like a TCP/IP stack.
Both LwIP and NETXDuo have there (different) problems.
Since ThreadX was transferred to the Eclipse Foundation no updates or bug fixes where published. So at the moment I’m still pointing on FreeRTOS, waiting to see if the Eclipse Foundation is capable of a high quality support as comes from FreeRTOS (now owned by AWS, but still maintained by its founder Richard Barry).
Martin

[mbarg.1]

Probably you are right, my experience focus on connected devices (where bugs are fatal)  and I agree this can be a limit, probably FreeRTOS alone can be ok, also because it it lighter than AZRTOS. Let us wait and see what happen; I also agree that ThreadX need to wake up and let us know if they intend to become a player in OS arena or not.

[ASEHST · Accepted solution]

Hello @kosh04,

Could you please try to add the following line in the FreeRTOSConfig.h file: 

#include CMSIS_device_header

Please let me know if this resolves the problem.

With Regards,

[kosh04]

Thank you! I actually had to add it to the FreeRTOS.h file I appreciate it nonetheless