zephyr

Build, configure, test, and debug Zephyr RTOS applications with west and CMake.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill zephyr-awfixers-stuff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zephyr
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/zephyr
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill zephyr-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide concise, actionable guidance for developing, configuring, testing, and debugging applications that use the Zephyr RTOS so engineers can move from workspace setup to flashing and host-simulated testing without guesswork.

Core Features & Use Cases

  • Workspace and toolchain setup with west and Zephyr SDK, including manifest management and dependency updates.
  • Application configuration using Kconfig fragments and devicetree overlays, plus guidance for integrating logging and runtime backends.
  • Targeted workflows for native_sim host testing and for flashing and debugging hardware using west, OpenOCD, and GDB; example: build and run hello_world on native_sim for CI tests, then re-use the same build steps to flash an nRF52840 DK and start a GDB session.

Quick Start

Build and run the Zephyr hello_world sample on native_sim and then show how to flash the same build to an nrf52840dk using west.

Frequently Asked Questions about zephyr

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

FAQPage Schema
How do I build and test a Zephyr RTOS application using native_sim?

Build Zephyr RTOS applications for native_sim by configuring CMake and west, enabling host-based execution and testing without physical hardware setup. This workflow uses west to initialize the workspace and run the compiled simulation locally for CI validation.

How do I configure devicetree overlays and Kconfig fragments in Zephyr?

Configure Zephyr RTOS hardware and application behavior by applying devicetree overlays and Kconfig fragments during the west build process. This allows customizing target-specific hardware bindings and enabling software features without modifying the core source tree.

What is the best way to debug Zephyr RTOS firmware with GDB and OpenOCD?

Debug Zephyr RTOS firmware by flashing hardware with west and attaching GDB through OpenOCD. This workflow connects the hardware debugger to your physical development kit, allowing breakpoint insertion and memory inspection during runtime.

How do I set up a Zephyr RTOS workspace and manage dependencies with west?

Initialize a Zephyr RTOS workspace using west manifest management to clone repositories and install Zephyr SDK toolchain dependencies. This standardizes the project environment and ensures all required modules are updated correctly before building.

Can I configure logging output in Zephyr RTOS using prj.conf?

Yes, Zephyr RTOS logging is configured by modifying prj.conf with Kconfig fragments to enable specific log levels and select runtime backends. This directs debug output to consoles or other transport mechanisms during execution.

Why does my Zephyr RTOS build fail when switching from native_sim to hardware flashing?

Switching from native_sim to hardware flashing requires updating devicetree overlays and prj.conf for the specific target board. Ensure the west build command targets the correct board and the Zephyr SDK toolchain matches your hardware architecture.