Getting Strange New Displays and Sensors Running on Zephyr for Open Health Devi...
summary
Zephyr is used to run displays and sensors across RP2040, nRF5340 and STM32 platforms with one codebase; custom drivers get written for weird panels and ten new sensors. Claim: sampling moves from 128/256 Hz up to 2,000 samples per second per channel and works by pushing data over Zbus and RTIO. Gotchas include XIP/QSPI keeping flash powered and MCU boot failures; LVGL integration and video‑mode DSI displays eventually work.
AI-written summary · about
chapters (16)
- 0:00Open health devices and Proto Central
- 3:22Open source hardware in medical devices
- 7:10Health devices and Zephyr's role
- 11:06Nordic's Zephyr adoption
- 12:50Scaling health devices with Zephyr
- 15:46Multi-threaded sensor data in Zephyr
- 17:12Nordic nRF5340 challenges
- 19:00Multi-core systems in Zephyr
- 20:27Display interfaces and complexities
- 23:20Display drivers for Zephyr
- 25:29MIPI DSI and video mode displays
- 27:35Displays with LVGL in Zephyr
- 30:06Out-of-tree sensor drivers in Zephyr
- 31:56Asynchronous sensor data with RTIO
- 33:45Lessons from Zephyr drivers
- 34:49Conclusion and future
related talks
40mGetting Strange New Displays and Sensors Running on Zephyr for Open Health Devi...
41mZephyr for Open Source Health Devices
43mZephyr for Open Source Health Devices
27mIntroducing a New Zephyr Sensing Subsystem
37mZephyr: A Game Changer for the Automotive Industry
34mZephyr-friendly Embedded Display Shopping Guide
39mA Slice of Zephyr Pi!
25mChallenging Hardware Contests With Zephyr and Lessons Learned