A Zephyr User Story
summary
Three years of hands-on results: a bare-metal product shipped in 12 months, the Zephyr rewrite in 9 months, and a new sensor node moving from prototype to CE-ish testing in about six months. Uses Zephyr SDK, device tree board support, the shell for debug, protobuf as a submodule and CI for builds. ported bare-metal to Zephyr and upstreamed an RTC driver improved maintainability; custom flash drivers remain a pain and the network stack and low‑power hooks need extra device-specific work.
AI-written summary · about
chapters (20)
- 0:00Zephyr user story intro
- 1:51Bare-metal at ProGlove
- 3:37Zephyr for streamlined dev
- 6:51Joining Blick hardware
- 8:38Low-power sensor needs
- 9:20Prototype to cert in 6mo
- 10:03Startup dev lessons
- 11:47Upstreaming code matters
- 13:12Network stack custom API
- 15:01Zephyr for fast startups
- 17:15Zephyr community benefits
- 18:42Zephyr vs other RTOS
- 20:06Shipping fast with Zephyr
- 21:29Community support benefits
- 23:14Upstreaming quality impact
- 23:55Zephyr network challenges
- 24:37Zephyr low-power limits
- 26:23Driver porting experiences
- 27:51Handling Zephyr updates
- 30:25Q&A
related talks
30mZephyr ❤️ Internet: How Zephyr Speeds Implementation for New IoT Devices
09mZephyr RTOS in Industry Research & Product Development
40mHow I Fell in Love with Zephyr – a System Architect’s Tale
49mThe Zephyr™ Project – An Updated Overview
34mWar Story: Using Zephyr Project to Develop a Wearable Device
45mLeveraging Zephyr RTOS for modern embedded systems: a perspective from education and research
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection