Skip to main content
erik23
Associate
Jul 29, 2026 4:33 PM UTC
Solved

ThreadX support for STM32CubeMX2

I see the USBX/FileX/LevelX middlewares are supported in STM32CubeMX2, but ThreadX (formerly AzureRTOS, formerly ThreadX) itself is not? Is ThreadX support on the roadmap for the STM32C5 series? I really don’t want to have to go back to using FreeRTOS.

Andrew Neil
Andrew NeilBest answer
Super User
Jul 31, 2026 10:13 AM UTC

ThreadX is not part of the STM32CubeMX2 offer.

The question was, is it on the roadmap ?

 

EDIT: I guess that question is answered here:

TL;DR  ​@erik23  - No.

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.

5 replies

Andrew Neil
Super User
Jul 29, 2026 4:43 PM UTC

Remember that ThreadX is an independent open-source project - not specific to ST.

The fact that it’s not in MX2 doesn’t preclude using it “manually” ...

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Oussama_TROUDI
ST Technical Moderator
Jul 31, 2026 9:45 AM UTC

Hello ​@erik23 

Thank you for your question.

At this stage, STM32CubeMX2 supports FreeRTOS and ThreadX is not part of the STM32CubeMX2 offer.

Best regards,
Oussama

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Andrew Neil
Andrew NeilBest answer
Super User
Jul 31, 2026 10:13 AM UTC

ThreadX is not part of the STM32CubeMX2 offer.

The question was, is it on the roadmap ?

 

EDIT: I guess that question is answered here:

TL;DR  ​@erik23  - No.

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
erik23
erik23Author
Associate
Jul 31, 2026 11:34 AM UTC

Thanks for posting that link. From the ST Developer answer towards the bottom of that thread, it sure seems like the ThreadX license changing to MIT played a part, otherwise why call that out in the justification for dropping ThreadX.