Improving System Configuration for Zephyr and Beyond
summary
Zephyr currently stores board specifics as scattered Kconfig entries and hard coded structures so adding UARTs or GPIOs forces code edits; proposal replaces most of that with Device Tree source compiled and parsed to generate unified C include files and Kconfig snippets. A Python tool using pyfdt parser reads DTBs produced from DTS for NXP Freedom and TI boards and emits C structures and #defines, aiming to remove duplicate config and auto-enable drivers while noting a compiled DTB can be 4–8 KB which is large for constrained Cortex‑M flash.
AI-written summary · about
chapters (8)
- 0:00The limitations of Kconfig
- 3:46Introducing device tree
- 6:06Device tree blobs and parsing
- 8:03Tooling and file integration
- 10:32Current development progress
- 12:49Driver integration goals
- 13:43Demonstrating a DTS example
- 22:01Q&A and architectural discussion
related talks
46mDevice Tree in Zephyr Project
44mConfigure Zephyr: Kconfigs and Devicetree in Simple Words
41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
44mConfigure Zephyr: Kconfigs and Devicetree in Simple Words
43mBeyond Static Devicetrees: Implementing Runtime Hardware Dynamism in Ze...- 41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
29mChallenges in Device Tree Sync - kernel, Zephyr, U-boot, System DT
42mEnabling Zephyr on Your Hardware Platform