Execution and memory
ESP32-S3 boot, flash, QIO, octal PSRAM, timers, reset, NVS, and bounded debug.
Browser-operated hardware workbench
Run the firmware.
Then meet the hardware.
Upload a real merged ESP32-S3 image, boot it inside an isolated native worker, and inspect the display, keyboard, buttons, serial output, sensors, power state, memory, and CPU before you flash a device.
- Targets
- Cardputer ADV · StickS3
- Worker
- ESP32-S3 QEMU · isolated
- Retention
- Ephemeral by default
01ValidateMerged flash image
02BootNative ESP32-S3 worker
03ObservePixels · UART · CPU
04InteractKeys · IMU · power
Explicit fidelity
A simulator that says what it knows.
Deterministic development surfaces are modeled and tested with owned conformance firmware. Physical claims stay with physical hardware.
Device surfaces
ST7789 framebuffers, Cardputer keyboard IRQs, StickS3 buttons, and UART.
Environment
Deterministic BMI270 samples and logical M5PM1 battery, VIN, and charging state.
Reality checks
RF, current draw, thermals, acoustic output, noise, calibration, and final flashing.
Hostile-input boundary
Your firmware is treated as untrusted—and temporary.
Each worker receives no host route, no capabilities, read-only runtime inputs, and one writable session directory. Uploads, flash state, sockets, and screenshots are destroyed when the session ends.
Inspect the public security contract →PublicBrowser
PrivateAccount gateway
Per sessionQEMU namespace
- No network
- 0 capabilities
- Private scratch