Zephyr Build System: Sysbuild and New Hardware Model
summary
Describes a new hardware model V2 that splits board and SoC data into YAML and Kconfig so boards become reusable and locate as board/SoC/cluster/variant, replacing the old locked arch-based layout; introduces sysbuild (system build) which can build, sign, align offsets and flash multiple images (multicore or multi‑SoC) together via West/CMake, reuses Zephyr CMake and twister, supports out‑of‑tree variants and qualifier overlays, and enforces centralized Kconfig for MCUboot keys and offsets so multi‑image builds stay consistent.
AI-written summary · about
chapters (14)
- 0:00Zephyr’s new hardware model
- 2:00Old hardware model limits
- 5:44New hardware model terms
- 13:02Benefits of new model
- 14:26Sysbuild for multi-image
- 17:18Sysbuild and Zephyr integration
- 21:03Extending boards with V2
- 26:51Sysbuild settings control
- 31:21Lessons from multi-image work
- 36:06Integration with TF-M
- 39:02Binary blobs in Sysbuild
- 40:45Future features and images
- 41:27Converting boards to Sysbuild
- 43:15Summary
related talks
29mBuilding Zephyr using Yocto
42mTaking Your Hardware to Production with Zephyr RTOS
55mBuild Heterogenous System Using Yocto Project
26mBuilding for Heterogeneous Systems
32mLeveraging Cloud Technologies for Development and Operation of Zephyr
33mContinues Integration Practices for Zephyr Upstream
33mContinues Integration Practices for Zephyr Upstream
37mManifests: Project Sanity in the Ever-Changing Zephyr World