Live data from Hacker News

Microsoft open-sources ThreadX

theregister.com

71–80 of 139 posts

Re: Microsoft open-sources ThreadX

#71

This was "Azure RTOS", bought by Microsoft in haste after Amazon acquired FreeRTOS. Bill Lamie left to start PX5 and work on a new lightweight embedded RTOS and took most of the talent with him. If Microsoft is doing this, they're pretty much walking away from their roadmap for Azure RTOS and IoT nodes along those lines. I call it a win, ThreadX had a lot more ecosystem behind it than FreeRTOS ever did. And it does r…

Yeah, it feels like getting rid of it.

I never understood why they got it, when they already had Azure Sphere OS.

At least they are open sourcing it, instead of leaving it in some digital vault.

Re: Microsoft open-sources ThreadX

#72

This was "Azure RTOS", bought by Microsoft in haste after Amazon acquired FreeRTOS. Bill Lamie left to start PX5 and work on a new lightweight embedded RTOS and took most of the talent with him. If Microsoft is doing this, they're pretty much walking away from their roadmap for Azure RTOS and IoT nodes along those lines. I call it a win, ThreadX had a lot more ecosystem behind it than FreeRTOS ever did. And it does r…

It's an acquisition from 2017 but do you happen to know why Amazon bought FreeRTOS?

My belief is that Amazon sees IoT as a way to further grow AWS backend services. All those nodes need a cloud, somewhere.

Taking stewardship of FreeRTOS allows them to develop a SDK, with or without a hardware kit included, to encourage IoT developers to lock into the Amazon ecosystem.

https://docs.aws.amazon.com/freertos/latest/userguide/c-sdk....

Microsoft saw this chain of events and panicked, buying up ThreadX to create Azure RTOS. I believe MS is now abandoning this path and focusing on other green fields...the recent events with OpenAI being a huge signal.

Re: Microsoft open-sources ThreadX

#73

Earlier quoted context omitted.

ThreadX has been around for 25 years. You licensed it and put it in your embedded system. It's in a lot of products.

But how many people agreed to sign an NDA in order to cluster fuzz such a critical low-level firmware binary blob component? Is this like another baseband processor?

Is it like another Intel ME, phone modem firmware, etc? Absolutely!

Everything from your x64 CPU to microSD to credit cards(not the readers; readers run antiquated Android and soon known-bad Chromium) runs some form of weird slow proprietary RTOS. It is what it is. I bet it takes ~century with help of superhuman AI to make those run an open and verified code. The situation is improving too, slowly, because using buggy proprietary code is not a goal, but means.

It's ok to be disgusted about the status quo, but that is not necessarily worth your time; IIRC one of original complaints by RMS on the state of software freedom that lead to Free Software Movement was about some HP printer running buggy custom OS. Even the point people said enough is enough goes back that far.

Re: Microsoft open-sources ThreadX

#75

how does threadx compare to zephyr,now both fully open sourced,one under eclipse another under Linux foundation

Zephyr is a lot more complicated than ThreadX and has been trying to get safety certified for many years now. It does have a really nice testing and board package story though, along with many other features ThreadX doesn't have.

Like running a sample on a supported board with Zephyr is pretty trivial. With ThreadX it seems to be included in the vendor sdk much like freertos might be. Some pros and cons to each certainly.

Re: Microsoft open-sources ThreadX

#76
post #73

Earlier quoted context omitted.

But how many people agreed to sign an NDA in order to cluster fuzz such a critical low-level firmware binary blob component? Is this like another baseband processor?

Is it like another Intel ME, phone modem firmware, etc? Absolutely! Everything from your x64 CPU to microSD to credit cards (not the readers; readers run antiquated Android and soon known-bad Chromium) runs some form of weird slow proprietary RTOS. It is what it is. I bet it takes ~century with help of superhuman AI to make those run an open and verified code. The situation is improving too, slowly, because using bug…

Gosh, there's so much wrong here.

> weird slow proprietary

They're often not weird, a simple single task runner with a few libraries to handle common tasks and cryptographic operations. Very simple, lightweight, and they generally share a common high level architecture (there's not much variation in an RTOS)

They're often not slow, they're minimalist OSes - barely qualifying as an OS if at all - designed to run a single task, with time guarantees, and to get out of the way. In fact, if it's a single task you need to run, they're faster than any general purpose OS - by design!

They're often not proprietary - a handful of RTOS with huge market penetration used in billions of devices (and now ThreadX) - are open source and have permissive licenses. What IS often proprietary about them are BSPs, but that's a whole separate issue. Yes, there are a lot of proprietary ones out there, but as a blanket statement, it's simply not true.

> readers run antiquated Android

Many use a stripped down version of AOSP, which has become a de facto standard BSP, yes. But many, many others do not (usually a flavor of embedded linux, or an RTOS).

> about some HP printer running buggy custom OS

It was a Xerox printer, and it was because he was frustrated from adding existing job management and notification features he had written to the new printer.

Re: Microsoft open-sources ThreadX

#77
post #75

how does threadx compare to zephyr,now both fully open sourced,one under eclipse another under Linux foundation

Zephyr is a lot more complicated than ThreadX and has been trying to get safety certified for many years now. It does have a really nice testing and board package story though, along with many other features ThreadX doesn't have. Like running a sample on a supported board with Zephyr is pretty trivial. With ThreadX it seems to be included in the vendor sdk much like freertos might be. Some pros and cons to each certa…

Any experience with Riot OS?

https://www.riot-os.org/

Re: Microsoft open-sources ThreadX

#78
"Every once in a while, a new open source initiative comes along which is truly an industry changing event" - the article

"Every once in a while, a revolutionary product comes along that changes everything" - steve jobs announcing the iPhone in 2007

Re: Microsoft open-sources ThreadX

#80
post #25

This was "Azure RTOS", bought by Microsoft in haste after Amazon acquired FreeRTOS. Bill Lamie left to start PX5 and work on a new lightweight embedded RTOS and took most of the talent with him. If Microsoft is doing this, they're pretty much walking away from their roadmap for Azure RTOS and IoT nodes along those lines. I call it a win, ThreadX had a lot more ecosystem behind it than FreeRTOS ever did. And it does r…

TIL Amazon acquired FreeRTOS.

Yeah, I had no idea. That's ... worrying.
Post reply on HN