From Pre‑Silicon To Production: Firmware Development on Zephyr
summary
Production PMIC firmware moves to Zephyr and a single unified firmware stack replaces two divergent RTOS codebases, letting the same application run on Raspberry Pi Pico and a custom PMIC evaluation kit over I2C and interrupt lines. Twister plus a Pytest harness runs Twister-based Hardware-in-loop tests (PIPPO plug‑in/plug‑out cycles, five iterations) from CI as a gating test, cutting duplicate work, catching real-device bugs pre‑silicon, and keeping bring‑up on schedule.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:22Agenda
- 1:05Key terms explained
- 3:34Pre-silicon testing importance
- 5:25Problem with parallel stacks
- 7:30Zephyr as the solution
- 9:17Unified firmware with Zephyr
- 11:03Pre-silicon hardware setup
- 12:30Automating tests with Twister
- 14:14Hardware-in-loop validation
- 15:21Twister test execution steps
- 18:11PIPPO test cycle details
- 22:00Twister in CI pipelines
- 24:07Results of unified approach
- 25:31Project success story
- 26:33Key takeaways
- 27:36Future Zephyr plans
- 28:59Q&A
related talks
42mTaking Your Hardware to Production with Zephyr RTOS
39mA Slice of Zephyr Pi!- 39mA Slice of Zephyr Pi!
43mZephyr for Open Source Health Devices
01h 19mMini-conference: RISC-V Support in Zephyr
57mZephyr RTOS Debugging and Performance Analysis
30mSoC Development: From ROM to Application
09mZephyr RTOS in Industry Research & Product Development