Keynote: The Rise of Frameworks in Zephyr: From Devices to Subsystems to Frameworks
summary
Claims that Zephyr is evolving from kernel services into reusable frameworks, backed by concrete work: a sensing framework with Google in early integration, SOF audio integration moved from vendor RTOS into Zephyr and now runs across ARM x86 and RISC‑V, and an embedded controller reference stack that OEMs adopt. Examples of contributed tools include logging, shell, and power management from Nordic. Focus is on implemented subsystems, cross‑architecture support, and which pieces are production ready versus prototypical.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04OS to reusable frameworks
- 3:13RTOS challenges and duplication
- 4:58Zephyr’s middleware evolution
- 6:47Benefits of reusable subsystems
- 8:35Specialized frameworks for products
- 10:04Emerging frameworks examples
- 12:12Embedded controller framework
- 13:37Upstreaming generic components
- 15:26Standardization versus innovation
related talks
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
15mLightning Talk: A Reusable Zbus Based Architecture, Abstracting Core Application Components
53mField Report: Setting up a Software Product Line (SPL) Architecture based on Zephyr
30mCombining Zephyr & C++20 to Build Safe, Low-footprint, Event-based Applicati...
32mArchitecting an IoT Product Line: Part 1 - Scoping
41mFuture of Zephyr Device Model
22mTowards a frameworkless world- 15mA Reusable Zbus Based Architecture, Abstracting Core Application...