How I Fell in Love with Zephyr – a System Architect’s Tale
summary
Claims that Zephyr plus disciplined modeling lets a 12‑year embedded workflow become manageable: Kconfig-driven builds and Kconfig templates standardize options; device tree overlays capture hardware variants so firmware source never changes; a project moves between control board, two peripheral-board revisions and Nucleo replacements while supporting about 200 rigs and three modules — heater, motor, AFE — with nine‑month porting pain reduced to configuration. A Raspberry Pi 4 swap works with three lines of change and the system boots.
AI-written summary · about
chapters (13)
- 0:00Introduction to Zephyr
- 3:13Embedded anti-patterns
- 8:53Product development complexity
- 11:02Agile hardware origins
- 17:22Zephyr’s architecture fit
- 22:19Device tree journey
- 26:55Supply chain flexibility
- 31:51Real-time vs application layers
- 33:16Zephyr love story
- 34:41Bridler project and future
- 35:56Q&A: Schematic literacy
- 39:16Q&A: Breaking habits
- 40:18Closing remarks
related talks
31mA Zephyr User Story
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
25mChallenging Hardware Contests With Zephyr and Lessons Learned
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
01h 05mBoF: Unlocking Software Defined Power Electronics with Zephyr: Concepts...
02h 02mTutorial: Hands-on with Zephyr-based IoT Hardware - Data Goes in, Dat...
18mKeynote: The Power of Consistency