Migrating an embedded systems lab to Zephyr: an experience report
summary
University courseware migrates from embOS (end-of-life) to Zephyr 4.1 to keep vendor support and student relevance, porting a custom STM32F7 application shield with buttons, Neopixel, display, SDS01 particle sensor and buzzer; development uses PlatformIO in VS Code and a supplied hardware test program on GitHub to validate drivers. Students learn device tree and Kconfig (typos are a frequent, time‑consuming bug), integrate Simulink/Embedded Coder for model‑based workflows, most choose Zephyr for final projects, and the migration proves workable though device‑tree pedagogy needs more lab time.
AI-written summary · about
chapters (9)
- 0:00Embedded systems lab migration
- 3:38Current setup
- 7:29Choosing Zephyr RTOS
- 8:34Course and lab redesign
- 11:05PlatformIO as development environment
- 12:33Teaching Zephyr
- 14:48Student projects
- 16:11Lessons learned
- 18:25Q&A on Arduino, MicroPython, PlatformIO
related talks
12mLightning Talk: Zephyr in Education
21mLearn Operating Systems Theory While Working with Zephyr
48mFrom FreeRTOS To Zephyr: A Practical Migration Guide for Embedded Developers
31mA Zephyr User Story
48mZephyr Project on Beetle
47mSponsored Session: Does Zephyr Scare the Bare Metal Embedded Developer World?
31mA Zephyr User Story
40mGenerate, Develop and Visualize Zephyr Platforms and Apps with Visual System Desi...