How to extract a bare metal flavor of code out of Zephyr to use in RTOS?
summary
Argues for a “Zephyr‑first” workflow and shows a case of extracting a Zephyr peripheral driver into a bare‑metal/other‑RTOS build by using the Zephyr device tree include generation script, separating drivers into a split low/high driver layout, and keeping register access and ISRs OS‑agnostic. Covers tooling that helps (west, twister, CI), painful gaps to solve (clock/power frameworks, sleep APIs, devicetree/Kconfig coupling), and the reality that certifications still require revalidation.
AI-written summary · about
chapters (7)
- 0:00Introduction to Zephyr and RTOS
- 7:31Traditional bare metal to RTOS flow
- 15:51Challenges with vendor HAL approach
- 20:08Zephyr-first driver development
- 27:55Benefits of Zephyr frameworks
- 32:12Q&A and community discussion
- 39:38Closing and break
related talks
47mSponsored Session: Does Zephyr Scare the Bare Metal Embedded Developer World?
48mFrom FreeRTOS To Zephyr: A Practical Migration Guide for Embedded Developers
42mTaking Your Hardware to Production with Zephyr RTOS
42mEnabling Zephyr on Your Hardware Platform
31mA Zephyr User Story
20mAbusing zephyr and meta-zephyr
33mImproving System Configuration for Zephyr and Beyond
27mZephyr Porting Efforts in High Performance SoCs