Zephyr for Open Source Health Devices
summary
Built several open hardware products (HealthyPi 5, HealthyPi 6 and the wearable HealthyPi Move) that run the same source tree on different MCUs, replacing Nordic/STM/Arduino SDKs with Zephyr and producing separate binaries per platform. Key solutions: single Zephyr codebase across three microcontroller platforms, power-saving event flow via Zbus event channels and RTIO-based asynchronous sensor reads with DMA and interrupts, XIP and link-time loadable modules to manage flash/RAM tradeoffs, and handling a sampling jump from 128 SPS to 3000 SPS. Firmware and devices are open source and operational.
AI-written summary · about
chapters (7)
- 0:00Zephyr and open source health devices
- 3:54Why open source health hardware matters
- 7:52Transitioning from vendor SDKs to Zephyr
- 13:35Moving to mainline Zephyr for portability
- 22:34Zephyr’s modular design and portability
- 27:41Conclusion and benefits
- 28:22Q&A on firmware scaling and certification
related talks
41mZephyr for Open Source Health Devices
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
40mGetting Strange New Displays and Sensors Running on Zephyr for Open Health Devi...
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
37mZephyr: A Game Changer for the Automotive Industry
50mZephyr Project: An RTOS to Change the Face of IoT
30mZephyr ❤️ Internet: How Zephyr Speeds Implementation for New IoT Devices
14mWhat is Zephyr and Where Is It Heading To?
