2024-09-06 10:14 AM - edited 2024-09-06 02:09 PM
Hi All,
Not so long ago ST has selected Microsoft ThreadX as one of its its strategic technologies.
In my opinion it is a very good RTOS. The problem is that it was supported by Microsoft only, no other community project integrates with it, e.g. mcuboot etc. It is almost like ThreadX does not exist.
Now, Microsoft ThreadX is Eclipse-ThreadX. It is open-source, MIT licensed but last Github commit was made 6 months ago. The latest version is 6.4.1 while ST is still stacked with version 6.2.0.
No significant ST 's commitment is visible. It does not look good - regretfully, I need to say.
Am I missing something?
I need to decide whether I should use it in my project or abandon while I still have a choice.
2024-09-06 10:32 AM
If your project has a long timeline and requires extensive community support and ecosystem integration, it will be wise to consider alternatives like FreeRTOS or Zephyr.
2024-09-06 11:25 AM - edited 2024-09-06 02:14 PM
@liaifat85 That is what I start to think. There are no signs ST wants to pick this ball up, probably eventually ST will drop ThreadX and go back to FreeRTOS or switch to Zephyr, unless something more exotic will gain sympathy of some VP detached from reality.
2024-09-06 03:07 PM - edited 2024-09-06 03:21 PM
Unfortunately this is "the Microsoft Way". Most of their affairs with acquired projects or companies... Anybody remembers what they did with Nokia? Skype? Now their darling is Rust.
So the status: free cheese is not forever. Future: expect more hard work.
2024-09-06 06:52 PM
You will find plenty of dysfunction on the zephyr repo as well. and there's the epic malloc bug saga for FreeRTOS that took place on this forum, and is still in a murky state.
No free lunch.
2024-09-07 12:51 AM - edited 2024-09-07 01:45 AM
@Pavel A. Particularly painful was how Microsoft cancelled Silverlight after when Miguel de Icaza demonstrated Mono/Moonlight on Android. Ofc, the official reason was different but I know for certain. I lost startup company, more than a year of work and considerable money and will never trust them again.
2024-09-07 12:54 AM - edited 2024-09-07 05:53 AM
@BarryWhit This is why I hesitate. ThreadX appears to be stable, well-thought, consistent, well tested and well certified. I mean, quite solid piece of software. Too bad probably it is going to be abandoned.
I am on the fence and ST is silent.
2024-09-07 05:55 AM
@TDJ Yes there were the times. Churn and huge waste of resources is unavoidable in this industry. Been in the WiMax project. But guess what - my current job is "powered by" Microsoft ))
2024-09-07 08:58 AM
ST isn't making a contractual commitment to ANY of this. You get to own your own decisions and choices.
Microsoft is a sh**ty partner, have been for decades, I wouldn't tie any of my business to them, ever.
Provided there's not bit rot, there's no reason you can't adopt a current release, and maintain and patch that yourself. We're not building Adobe Flash
2024-09-07 11:55 AM
@Tesla DeLorean Exactly, ThreadX is no longer Microsoft and it is MIT licensed.
RTOS does not need to be the best. I do not work for SpaceX (yet). It just needs to be good enough.
Thank you for your input.