Platforms

Simulators

CHERI simulators range from specification-linked reference models to full-system emulators used for compiler work, operating-system bring-up and automated testing.

For
Developers, architects, product leaders and procurement teams
Last reviewed
2026-08-05
Review cycle
Review every 6 months

Overview

CHERI simulators range from architectural reference models to fast full-system emulators. They support compiler work, OS bring-up, automated tests and architecture experiments before hardware is available.

Use a simulator to shorten the feedback loop, not to avoid stating what remains untested. Document whether the model represents instruction semantics, devices, operating-system boot, timing or microarchitecture, then move hardware-dependent conclusions to an FPGA or silicon route when necessary.

Best fit

Choosing the right model balances fidelity, speed, device support and ease of integration.

What to evaluate

1. Reference

Use a specification-linked model when exact instruction semantics and conformance matter.

2. Full system

Use QEMU-CHERI or a provider model when booting an OS and running realistic software is the goal.

3. Workflow

Pin model, platform, firmware, image and toolchain revisions; automate startup and output checks.

Check current status

A simulator may omit timing, power, analogue behaviour, devices or microarchitectural effects. Validate hardware-specific conclusions separately.

Verify availability, maturity, specifications, software support and lifecycle terms with the current platform owner before procurement.

Provider and project sources

Try it

Pick the fastest model that represents the property under test and document what it does not represent.

Run the first simulated system