[flagged]
Microsoft open-sources ThreadX
11–20 of 139 posts
Re: Microsoft open-sources ThreadX
#12This 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…
But are there devs for the acquired platform now?
The article says ThreadX used to be what Intel Management Engine ME ran on? How do I configure the ME / AMT VNC auth in there?
Re: Microsoft open-sources ThreadX
#13It'll be really interesting to see how this shakes out in terms of other open rtos projects given a safety certified RTOS is now available under a nice license with wide architecture support.
Re: Microsoft open-sources ThreadX
#14For those wondering why Azure has an RTOS, Microsoft bought Express Logic and their ThreadX RTOS in 2019. ThreadX is in use on a large number of resource constrained microcontrollers.
The Azure branding makes little sense, beyond maybe that IoT things communicate with the cloud or something.
Re: Microsoft open-sources ThreadX
#15> At this point, only the current version is on GitHub, and we don't see any trace of a VideoCore version. :( (This is the RPi boot blob) > Now, there is at least some hope that the Raspberry Pi Foundation might be able to get permission to release the source code for its version. Indeed that would be something!
I understand the notion here that opening up ThreadX will start to allow visibility into VideoCore, since ThreadX runs the thing. But an RTOS/scheduler is only a miniscule part of a GPU and since Broadcom never opens up anything, I believe it's a false hope. Opening up any GPU code, from any maker, invites patent lawsuits from competitors. And then the injunctions start flying.
Can confirm: same story for PowerVR. It's a double whammy: They want the driver licensing revenue and they are afraid of patent trouble.
Re: Microsoft open-sources ThreadX
#16It took a lot of reading of that blogpost before I realized that it was about an operating system. I seriously thought it was about some parallel threading standard. Especially for a broad announcement like that, they should give readers some more context.
Re: Microsoft open-sources ThreadX
#17The safety certifications are particularly interesting. It's a lot of work to develop "safe software" - that is software that is developed according to a safety standard and certified to a "safety integrity level". Having an RTOS which is both open source and safety certified is pretty great. They say they want to maintain the certifications - that will be tricky unless there's some investment coming from somewhere.…
Yes, that ongoing certification will be costly but they mention the support of companies with pretty deep pockets: "In addition to the project, we are also announcing the creation of an interest group focused on developing an industry-supported, sustainable funding model for ThreadX. We are excited that AMD, Cypherbridge, Microsoft, NXP, PX5, Renesas, ST Microelectronics, Silicon Labs, and Witekio (an Avnet company) have all committed to supporting this conversation"
Re: Microsoft open-sources ThreadX
#18how does threadx compare to zephyr,now both fully open sourced,one under eclipse another under Linux foundation
Re: Microsoft open-sources ThreadX
#19Is it me or certification is a very powerful way to keep control on the open sourced code ? I mean it's open so you can modify it but as soon as you touch one line, you can't claim the certification anymore... Therefore only MSFT has the ability to change the code (because I suppose they don't have to re-do the whole certification); until another big player gets the certification.
Right ?
Re: Microsoft open-sources ThreadX
#20This 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…
But are there devs for the acquired platform now? The article says ThreadX used to be what Intel Management Engine ME ran on? How do I configure the ME / AMT VNC auth in there?
ThreadX has been around for 25 years. You licensed it and put it in your embedded system. It's in a lot of products.