The Native Simulator and Zephyr
summary
Zephyr builds as a host program by replacing the architecture layer so kernel threads map to pthreads and hardware is modeled as scheduled events, yielding deterministic fast runs, able to use GDB and valgrind/UBSan for real debugging and coverage. Native simulator supports multi-MCU images and Nordic nrf models, but busy-waits break (must sleep or use sync primitives), there is no MMU/user space, and host vs embedded C library choices force careful driver splitting.
AI-written summary · about
chapters (7)
- 0:00Native simulator intro
- 2:08Why native simulator exists
- 8:06How native simulator works
- 14:28Building for native sim
- 23:50Limitations and considerations
- 27:48Advanced driver use cases
- 35:18Q&A
related talks
47mThe Native Simulator and Zephyr
40mZephyr Off-Chip Peripheral Emulation
32mUsing Customerized QEMU Co-simulation for Development and Test of Zephyr Applications
37mStreamlining Testing with Generic Tests and Emulators
40mTesting Zephyr Bluetooth Devices at Scale
46mZephyr Application Development Using TDD: Getting Started
57mZephyr RTOS Debugging and Performance Analysis
18mKeynote: From Zephyr’s Structured Data to Traceable and Testable Open Hardware