Live data from Hacker News

Amazon FreeRTOS – IoT operating system for microcontrollers

aws.amazon.com

21–30 of 106 posts

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#21

Earlier quoted context omitted.

In this case it seems Amazon outright acquired whoever was maintaining FreeRTOS and has made it available under an MIT license: https://aws.amazon.com/blogs/opensource/announcing-freertos-... So presumably they have bigger plans beyond examples.

Richard Barry, founder of FreeRTOS, has joined AWS as a principal engineer, and will continue to support Amazon FreeRTOS. WITTENSTEIN high integrity systems (WHIS) will continue to support and develop OPENRTOS and SAFERTOS, commercial implementations of FreeRTOS for projects that require certification or support. Richard released FreeRTOS in 2003, and had been working on FreeRTOS in partnership with WHIS since 2006,…

I do hope they'll keep maintaining it - I've been working with an ESP32 lately and the stuff Espressif has been able to build using FreeRTOS as a base is nothing short of incredible. $7 for wifi and bluetooth on a development board.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#22
For those looking for context around this acqui-hire/stewardship, here's our take from late 2016 when Silicon Labs acquired FreeRTOS competitor Micrium:

Going forward, we expect to see non-traditional IoT software and infrastructure platform vendors looking closely at the embedded OS space. A compelling OS offering could drive millions of device signups for IoT services platforms, such as AWS IoT, Microsoft Azure, and GE Predix, which derive recurring revenue from services rendered to an installed base of devices. Onboarding an OS offering (or complementing Windows 10 IoT Core with an MCU-focused OS in Microsoft’s case) would allow these players to potentially hook analytics and connectivity services into a portion of the billions of MCUs that are shipped yearly, bumping up services revenue substantially.

We see this acquisition as a substantial, missed opportunity for leading MCU vendors, such as Renesas, Microchip/Atmel, and Qualcomm/NXP/Freescale, who we had shortlisted as likely acquirers. Micrium competitors Express Logic and WITTENSTEIN would be rational targets for the next round of RTOS acquisitions.

We had expected Microsoft to refocus its attention on the MCU space (perhaps with a derivative of WinCE) but they have been more focused on providing runtimes for maker boards and playing catch up with AWS, than building out the bottom end of their OS portfolio. Ditto Google with Android Things.

Think this is a great move on Amazon's part providing, but not forcing, an easy on-ramp to AWS for the billions of MCU-powered devices that ship every year.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#24
post #23

What's the advantage of a RTOS?

Been awhile since I dealt with microcontrollers, but my recollection is that some non-trivial amount of things have to be done by a RTOS.

For example if your thing is attached to a sensor that spits out 47 bytes of sensor data every N clock cycles, and has a buffer that is 94 bytes, then you damn well better be reading that thing every N*2 clock cycles with a hard guarantee that your routine is finished copying all 94 bytes of data by the time it finishes (including time for interrupts).

This gets complicated when you have specific requirements about when data is available or other things too (e.g. if reading data requires pulling pin X low, waiting at least Y clock cycles, and then reading all data in no more than Z clock cycles before returning pin X back to high, then good luck doing that in a normal OS where you have no hard time guarantees).

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#25
post #23

What's the advantage of a RTOS?

The advantage is that you can make claims about the maximum time it take to process something. Contrast that to Windows, macos, or Ubuntu that generally are zippy on new hardware, but sometimes the circle spins or the hourglass shows up and makes you wait, possibly for an outsized period of time for what is being processed.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#26
post #21

Earlier quoted context omitted.

Richard Barry, founder of FreeRTOS, has joined AWS as a principal engineer, and will continue to support Amazon FreeRTOS. WITTENSTEIN high integrity systems (WHIS) will continue to support and develop OPENRTOS and SAFERTOS, commercial implementations of FreeRTOS for projects that require certification or support. Richard released FreeRTOS in 2003, and had been working on FreeRTOS in partnership with WHIS since 2006,…

I do hope they'll keep maintaining it - I've been working with an ESP32 lately and the stuff Espressif has been able to build using FreeRTOS as a base is nothing short of incredible. $7 for wifi and bluetooth on a development board.

Additionally they are adding in things like native drivers for WiFi, BLE, and signed updates. AWS Version will be v5.0.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#27
post #23

What's the advantage of a RTOS?

The usual reason for using an RTOS on small embedded controllers is that a full OS is way too big to fit on such small CPUs (eg. 64K of RAM and 256K of FLASH is common). FreeRTOS is tiny - it only uses a few KB of FLASH. Non real time OSes also don't provide the timing guarantees that are often required in those kinds of applications.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#28

Earlier quoted context omitted.

It's a nice present from Amazon. They should keep doing this, I'd like a MIT licensed QNX next please. God knows they have the money.

GPL would be fine too; I'd just like something that actually qualifies as FOSS, rather than something proprietary.

GPL is also a non-FOSS license. It says it is, but its not.

Can't wait until the GPL is a rarely used license.

Re: Amazon FreeRTOS – IoT operating system for microcontrollers

#29
post #25
post #23

What's the advantage of a RTOS?

The advantage is that you can make claims about the maximum time it take to process something. Contrast that to Windows, macos, or Ubuntu that generally are zippy on new hardware, but sometimes the circle spins or the hourglass shows up and makes you wait, possibly for an outsized period of time for what is being processed.

To make any worthwhile claims you need the worst case execution time of your code. Even in the absence of multi-threading, technologies like caches or out-of-order execution can make this quite painful.

The common solution seems to be: Don't care for some missed values (e.g. non-safety critical systems) or over provisioning (absence of budget pressure).

-> A RTOS alone doesn't give you any reliable claims (but does make a lot of embedded stuff much easier).

Post reply on HN