Zephyr for Open Source Health Devices
summary
Open source patient monitors (HealthyPi 5, HealthyPi 6, HealthyPi Move) run a single Zephyr codebase across nRF, STM32 and RP2040 families, sharing drivers and modular sensor repositories; migration replaces vendor SDKs with Zephyr features like Zbus, the state-machine framework and async read/decode to handle DMA and triggers. Devices support up to 5 ECG channels at 3000 samples/sec, use MCUboot + LittleFS OTA over BLE, and a dual‑core M7+M4 design for display versus sampling. Most ports work but IPC/shared‑memory corruption and streaming API thread priority issues remain.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:10Open source health devices
- 7:10Healthy Pi evolution
- 10:05Zephyr migration challenges
- 15:28Development experience with Zephyr
- 20:30Sensor drivers and async API
- 27:06Porting and libraries
- 30:17Dual-core device design
- 33:30Zephyr benefits and conclusion
- 38:00Certification and safety
related talks
43mZephyr for Open Source Health Devices
40mGetting Strange New Displays and Sensors Running on Zephyr for Open Health Devi...- 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
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
49mThe Zephyr™ Project – An Updated Overview
39mA Slice of Zephyr Pi!