Which OS/RTOS makes sense for your Constrained Device?
summary
If Linux fits, use it — 62% embedded market uses Linux — otherwise choose between proprietary stacks, roll‑your‑own, or open projects; community activity and licensing matter more than marketing. Zephyr is rising with Zephyr 1.14 LTS, public security practices, POSIX support, a strong Bluetooth stack and 160+ boards supported; it targets safety certifications (IEC 61508). NuttX shows the largest raw commit history (~38,000 commits). Amazon FreeRTOS shows few upstream commits after AWS forks, so expect cloud‑lockin and different update workflows.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 7:14IOT OS landscape overview
- 11:05Criteria for choosing an OS
- 15:19Project governance and IP
- 20:16Licensing and legal risks
- 24:19Security and community health
- 28:46Comparative community trends
- 33:03Safety certification paths
- 36:43Zephyr project deep dive
- 43:43Summary and Q&A
related talks
38mRTOS vs Bare metal Dawn of Constrained Device
38mTo RTOS, or not RTOS: That is the Question
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
50mZephyr Project: An RTOS to Change the Face of IoT
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
29mFuture-proofed microcontroller designs with FreeRTOS
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
26mTo Boldly go Where Linux Cannot with Zephyr and Eclipse IoT