メニュー
Devicetree management for Zephyr RTOS. Covers syntax, bindings, overlays, Hardware Model v2 (HWMv2), and advanced node/property deletion patterns. Trigger when defining hardware topology, creating overlays, or mapping pins and peripherals.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Zephyr RTOS development — boards and devicetree, the build system (west, Kconfig, CMake, sysbuild), drivers and peripherals, BLE and networking, the kernel, storage, power, testing and debugging, security and OTA. Use this for ANY Zephyr RTOS or embedded-firmware task on a Zephyr project; it routes you to the right specialized skill via the zephyr-cli registry.
Custom board bringup for Zephyr RTOS using Hardware Model v2 (HWMv2). Covers directory structure, board.yml metadata, core configuration files (Kconfig, defconfig, CMake), and revision management. Trigger when creating new board definitions or porting Zephyr to custom hardware.
Build system management for Zephyr RTOS. Covers West workspace initialization, manifest management, Sysbuild multi-image builds, Kconfig symbols, and CMake integration. Trigger when setting up workspaces, configuring builds, or troubleshooting build-time errors.
Bluetooth Low Energy (BLE) integration for Zephyr RTOS. Covers GATT Services/Characteristics, GAP advertising, connection parameters, power optimization strategies, and the professional Send-When-Idle design pattern. Trigger when adding BLE connectivity, optimizing battery life for wireless devices, or implementing custom GATT profiles.
IP networking fundamentals for Zephyr RTOS. Covers IoT protocol selection (LwM2M, CoAP, MQTT), IP stack configuration and trimming (IPv4/IPv6, UDP/TCP), and professional SDK integration as Zephyr modules using West manifests. Trigger when building cloud-connected applications, optimizing network memory usage, or integrating external cloud SDKs.
USB and CAN connectivity for Zephyr RTOS. Covers USB device stack configuration (CDC ACM, HID, MSC), CAN controller integration, and professional USB-to-CAN adapter patterns including buffering and protocol packetization. Trigger when adding USB interfaces, implementing CAN bus communication, or building hardware diagnostic tools.
| name | devicetree |
| description | Devicetree management for Zephyr RTOS. Covers syntax, bindings, overlays, Hardware Model v2 (HWMv2), and advanced node/property deletion patterns. Trigger when defining hardware topology, creating overlays, or mapping pins and peripherals. |
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.