Taking Your Hardware to Production with Zephyr RTOS
summary
Zephyr RTOS is presented as a full production stack: start on dev boards with board files, device tree and menuconfig, iterate to a 10-unit pilot to validate board revisions and provisioning, then run a ~100-unit CM line with test points, programming stands and MCUboot for signed images. Use MCUboot over-the-air updates, PKI for device certificates, remote RPC to change log levels, RTT/Ozone/SystemView for debugging, and automated testing with pytest/twister/device_sim to catch regressions before scaling to fleets of 10,000+.
AI-written summary · about
chapters (8)
- 0:00Zephyr RTOS for production
- 1:03Production challenges with Zephyr
- 3:54Early prototyping
- 9:06First pilot run
- 14:23Scaling to 100 units
- 22:08Mass production cost
- 31:29Managing field devices
- 38:55Q&A firmware updates
related talks
01h 03mZephyr RTOS: Software power tools for constrained devices
09mZephyr RTOS in Industry Research & Product Development
45mLeveraging Zephyr RTOS for modern embedded systems: a perspective from education and research
57mZephyr RTOS Debugging and Performance Analysis
32mFrom Pre‑Silicon To Production: Firmware Development on Zephyr
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?
47mLinux and Zephyr, sitting in a tree (literally!)
30mSoC Development: From ROM to Application