To RTOS, or not RTOS: That is the Question
summary
Compares concrete tradeoffs: FreeRTOS small footprint (mature, modular kernel with many vendor drivers but growing AWS ties), Arm Mbed OS (CMSIS-based hardware abstraction, modular drivers, built-in MQTT/CoAP/TLS and flash-optimized filesystem), and Drogue IoT in Rust (Embassy async runtime, device+cloud+OTA stack). Contrasts those with bare-metal options like ESP32 dual-core using Espressif IDF (Wi‑Fi/Bluetooth, MQTT, optional FreeRTOS scheduler) and Arduino; notes real‑time guarantees, driver availability, memory/multitasking needs, and single‑vendor vs vendor‑neutral governance.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:56Types of Operating Systems
- 13:41To Mbed, or not Mbed
- 15:36FreeRTOS Architecture
- 20:39Zephyr Architecture
- 24:08OS-less Microcontrollers
related talks
38mRTOS vs Bare metal Dawn of Constrained Device
29mFuture-proofed microcontroller designs with FreeRTOS
49mWhich OS/RTOS makes sense for your Constrained Device?
37mTizenRT as Lightweight IoT Plaftorm
33mRIOT: The Friendly Operating System for the IoT (If Linux Won't Work, Try RIOT)
32mHeterogeneous Linux and RTOS Software Architecture for Low-Price RISC-V...
54mSqueezing Your Microcontroller
50mZephyr Project: An RTOS to Change the Face of IoT