liveBook · Manning

Emulation

As explained in Embedded Software with Rust

Emulation is the reproduction of a target system's behavior so software can run or be tested without the original hardware.

Emulation lets embedded firmware run and be tested in software without the original hardware. It is useful early in development, when boards are unavailable or hardware setup problems make it difficult to isolate software faults. section 1.7.2 section 2.7

An emulator can support rapid iteration, remote collaboration, automated regression testing, and continuous integration. Starting without a physical board can also avoid problems such as incorrect cables, wiring, or missing host drivers. section 2.7.1 section 1.7.2

Tools offer different ways to work without a physical target:

  • QEMU supports many ARM Cortex microcontrollers and can be used for software-level testing and validation. section 2.5.5
  • Renode simulates a range of boards and peripherals with fine-grained configuration. section 2.5.5
  • PICSimLab provides a graphical virtual-board environment; Wokwi provides web-based interactive prototyping and project sharing. section 1.7.2 section 2.5.5
Figure 1.7 PICSimLab virtual board
CH01 F07 Cabanis

A PICSimLab virtual board illustrates a graphical alternative to working directly with physical hardware. section 1.7.2

Treat successful emulation as an early check, not final hardware validation. An emulator may omit peripherals or board-specific behavior and generally does not guarantee cycle-accurate timing. Test timing-sensitive behavior and peripheral details on the actual device. section 2.7.1

How Embedded Software with Rust covers it

How deep it goes
Explains practical benefits and hardware fidelity trade-offs and introduces a QEMU workflow.
Examples
Illustrates virtual targets with QEMU and a PICSimLab virtual board, alongside Renode and Wokwi alternatives.
What it assumes
Assumes embedded programming experience while recommending an emulator for early exploration.
What you can do after
Apply it via QEMU to run and test embedded Rust firmware before validating on real hardware.
How it connects
Connects embedded firmware development with continuous integration, regression testing, and hardware validation.

Also explained in

Compare how 2 books explain emulation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Embedded Software with Rust. The section links point to the parts of the book it draws on.