4 ms·

It seems it is exactly freeRTOS, but with some additional drivers and libs so not changing the name seems to be a good decision I think. I am wondering however

by jore 9y ago

It seems it is exactly freeRTOS, but with some additional drivers and libs so not changing the name seems to be a good decision I think. I am wondering however if by using this os, the dev is obliged to use aws services. Isn't this more of a limitation than a benefit?

dvfjsdhgfv 9y ago
That's a fair question. There definitely are people not wanting the additional stuff from Amazon.
- nerfhammer 9y ago
  For example, probably most people using FreeRTOS thus far were using it for ordinary MCU stuff like listening for button presses and blinking LEDs without even involving a wifi transceiver at any point.
  - deleted 9y ago
    [deleted]
michaelt 9y ago
According to [1] "FreeRTOS remains open source, with no commitments. [...] FreeRTOS users are not required to be AWS customers in any way." Most likely Amazon's motivation is that they can make sure FreeRTOS makes using Amazon's services very easy; there are some IoT offerings that can't connect to Amazon's services, (or at least can't connect easily) [2] By making sure FreeRTOS can easily pull in the right libraries, they can make it easier for people to connect devices to AWS without compromising on secure encryption. [1] https://aws.amazon.com/blogs/opensource/announcing-freertos-kernel-v10/ https://aws.amazon.com/blogs/opensource/announcing-freertos-... [2] Last time I checked, Amazons MQTT service required TLS1.2 and an esp8266 only supported TLS1.1
- ronsor 9y ago
  The latest axtls port for esp8266 supports TLS 1.2.
rickycook 9y ago
i would assume it’s like amazon linux; rhel with extras to make amazonization easy... but freertos rather than rhel