From zephyr-skills
Manages Zephyr RTOS Devicetree including syntax, bindings, overlays, HWMv2, and node/property deletion patterns. Use for hardware topology definition, overlay creation, and pin/peripheral mapping.
npx claudepluginhub beriberikix/zephyr-agent-skills --plugin zephyr-moduleThis skill uses the workspace's default tool permissions.
The Devicetree (DT) is the source of truth for your hardware topology in Zephyr.
Guides custom board bringup for Zephyr RTOS using HWMv2: directory structure, board.yml metadata, Kconfig, defconfig, CMake configs, revision management. For new board definitions or hardware porting.
Delivers complete compilable firmware and peripheral drivers (I²C/SPI/UART/ADC/DMA) for ARM Cortex-M MCUs (Teensy, STM32, nRF52, SAMD) with architecture and concurrency guidance.
Share bugs, ideas, or general feedback.
The Devicetree (DT) is the source of truth for your hardware topology in Zephyr.
Nodes, properties, and phandles form the hierarchy.
&label), Properties (reg, status, compatible).Mapping hardware descriptions to driver schemas.
pinctrl.Modifying board behavior for specific application needs.
.overlay files, zephyr,chosen, variant-specific overlays.Deleting and redefining nodes/properties for product variants.
/delete-node/, /delete-property/./* app.overlay */
&i2c1 {
status = "okay";
};
&uart0 {
status = "disabled";
};
west build -t rom_report: See how devicetree definitions impact memory.build/zephyr/zephyr.dts: Inspect the FINAL resolved devicetree after all overlays are applied.build/zephyr/include/generated/zephyr/devicetree_generated.h: Inspect generated DT macros consumed by C code..overlay files.west build.build/zephyr/zephyr.dts.build/zephyr/include/generated/zephyr/devicetree_generated.h.dt_syntax.md: Core syntax and properties.dt_bindings.md: Binding definitions and compatible mapping.dt_overlays.md: Overlays, HWMv2, and deletion patterns.overlay_include_check.py: Overlay sanity checker.app_overlay_template.overlay: Baseline overlay template.