Working with the Community: A Timeline for Adding Support for a New Board in Zephyr
summary
Timeline and checklist for upstreaming a Zephyr board: expect toolchain merged in ~1 month before CI can build new targets; board work is ~80% Kconfig/DTS/yaml and 20% C drivers; Hardware Model v2 requires placing SOC/family/series/board files in the right directories; a minimal hello world needs UART plus pinctrl and clocks because DTs are compiled in; CI integration and SDK updates take about a week, full upstream merge often arrives around week five; send small PRs (≤5 patches), run checkpatch.pl, and get two reviewers.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:09Agenda
- 2:00Zephyr Release Cycle
- 4:35Tool Chain
- 7:30Board Support
- 9:30Hardware Module V2
- 17:22Family
- 17:58Series
- 18:48Config Navigation
- 19:50Board Overview
- 21:37Board YAML
- 22:34Hardware Description
- 23:59Getting Started
- 27:09The Code
- 27:19Documentation
- 28:38How to start
- 30:09Pool request
- 32:16Be patient
- 33:50Final thoughts
- 35:27Outtakes
- 36:09Questions
related talks
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
40mContributing to Zephyr vs (Linux and U-boot)
40mBoF: Zephyr: Meet the Maintainers
39mBoF: Meet the Zephyr Community
40m9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
36mHow to Get Your Zephyr Patches Merged
53mHow to Contribute a Zephyr Sensor Driver
41mZephyr Documentation BoF