devicetree

Manage Zephyr Devicetree definitions, bindings, and overlays with standard tooling.

59|13|Updated Feb 7, 2026

Search Tags:#bindings #overlays #zephyr #HWMv2 #devicetree #board-bringup #driver-bindings

Ready to run

npx skills add https://github.com/beriberikix/zephyr-agent-skills --skill devicetree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devicetree
Source: https://github.com/beriberikix/zephyr-agent-skills/tree/main/skills/devicetree
Command: npx skills add https://github.com/beriberikix/zephyr-agent-skills --skill devicetree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Devicetree skill helps teams define, validate, and modify hardware topology in Zephyr projects, reducing topology errors and iteration time.

Core Features & Use Cases

Understands DT syntax, node hierarchies, and labels to map hardware components.
Manages bindings, overlays, and HWMv2 strategies for board variants and drivers.
Use cases include adding or deleting nodes/properties across variants and validating final DT with builds.

Quick Start

Start by reviewing the core references (references/dt_syntax.md, references/dt_bindings.md, references/dt_overlays.md) and try a simple overlay on a sample board to see final dt in build/zephyr/zephyr.dts.

Frequently Asked Questions about devicetree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I apply devicetree overlays to customize a Zephyr board?▼

To apply devicetree overlays in Zephyr, you manage overlay files that modify the base board topology by adding or deleting nodes and properties. This skill parses DT syntax and maps hardware bindings to generate the final merged devicetree during the build process.

What is the best way to manage Zephyr devicetree bindings for new drivers?▼

Managing Zephyr devicetree bindings involves defining node hierarchies and labels that map hardware components to driver behaviors. This skill helps you understand binding syntax and apply HWMv2 strategies to ensure drivers correctly interact with your customized board variants.

Can I use devicetree overlays to create multiple hardware board variants in Zephyr?▼

Yes, you can use devicetree overlays to create hardware board variants in Zephyr. This skill supports applying overlay files across different board variants, allowing you to evolve the devicetree topology and validate the final hardware configuration through standard builds.

Why does my Zephyr devicetree topology fail to build after adding new nodes?▼

Zephyr devicetree topology builds often fail due to syntax errors or incorrect binding mappings in newly added nodes. This skill helps validate DT syntax, map hardware bindings accurately, and verify the final output in the generated build file to reduce topology iteration errors.

Where can I find the final generated devicetree file after a Zephyr build?▼

The final generated devicetree file is located in the build directory at build/zephyr/zephyr.dts. This skill guides you through applying overlays and bindings so you can review this generated file to verify your hardware topology and node modifications.

Does Zephyr HWMv2 require specific devicetree strategies for board bringup?▼

Zephyr HWMv2 requires specific devicetree strategies to effectively manage board variants and driver bindings during hardware bringup. This skill provides the necessary mapping and overlay application techniques to support evolving topologies under the HWMv2 hardware model.