Zephyr Native Simulation

Develop, test, and debug Zephyr applications with the speed and convenience of your host machine.

Core Workflows

1. Simulation Basics

Understand when to use native_sim vs. QEMU and how to map host resources.

• Reference: simulation_basics.md
• Key Tools: west build -b native_sim.

2. Host-Side Debugging

Use professional host tools to find the most elusive bugs.

• Reference: debugging.md
• Key Tools: gdb, valgrind, gprof, pcap.

3. Automated Testing (CI/CD)

The foundation of modern firmware development.

• Reference: See the testing-debugging skill (Phase 3) for comprehensive testing workflows.
• Key Tools: twister -p native_sim.

Quick Start

# Build for host
west build -b native_sim samples/hello_world

# Run the app
./build/zephyr/zephyr.exe

# Debug with GDB
west debug

Automation Tools

• native_log_scan.py: Scan native simulation logs for common crash/failure signatures.

Examples & Templates

• native_sim_ci_checklist.md: Starter checklist for CI simulation coverage.

Validation Checklist

• west build -b native_sim succeeds for at least one sample and one app target.
• Built binary runs on host and emits expected startup logs.
• Host debugger (GDB/Valgrind) can attach and surface expected symbols.
• Simulation test path is integrated into CI (for example Twister native_sim run).

Resources

• References:
  • simulation_basics.md: Architectural overview and usage patterns.
  • debugging.md: GDB, Valgrind, and profiling guide.
• Scripts:
  • native_log_scan.py: Failure signature scanner for native_sim logs.
• Assets:
  • native_sim_ci_checklist.md: CI simulation review checklist.