Flashing, testing, re-testing on the bench needed a human. Not anymore.
Oracova is an automated test bench for firmware.
Your unmodified binary runs on your real microcontroller.
Oracova emulates the world around it with real-time physics and injects faults.
Every run scored PASS or FAIL with captured evidence.
AI agents drive the bench, so the loop runs unattended.
Motors spin, packs heat up, pressure builds, so your unmodified firmware reaches every test point on its own. No test hooks, no forced states, no special builds. Common peripherals come as validated models from Oracova's open-source marketplace.
Commutation and hall-sensor faults on real silicon, proven on the Oracova bench.
The pack is physics, so protection logic is tested by reaching the fault, not by faking it.
Closed loops settle, overshoot, and fault against a plant that behaves like the real one.
Every run returns PASS or FAIL with captured traces and firmware hashes. A real run, the same one replaying at the top of this page:
A stuck hall sensor: unguarded firmware energizes the wrong phase, the guarded build shuts down clean. All five verdicts from the same fault library on the same two-MCU rig, real hardware, not a simulator. Full run report.
To the firmware, it is flying. Gyro and accel come from live physics; its motor commands move that world. Every board on Oracova gets the same: a simulator of its own world, faults included.
A DMA allocation failure every static check missed. Only the closed loop caught it.
"An AI cannot be trusted to judge firmware." Correct. Ours does not: the agent brings up the world and proposes scenarios; a deterministic, AI-free checker scores every run on real hardware. The model never grades your code.
| oracova | manual bench | simulator | HIL rig | |
|---|---|---|---|---|
| runs on real silicon | yes | yes | no | yes |
| runs unattended | agent-driven | no | yes | scripted |
| a bench per PR | yes | no | yes | no |
| faults on the chip | by physics | hand-wired | in a model | scripted |
| entry cost | a DUT board + bring-up | engineer-hours | "free" | $9,900+ |
Proven today: STM32F411 on the bench, a BLDC + hall fault library, unmodified Betaflight in closed loop. DUT boards are built per part; new targets are bring-up work, not a catalog.
I have shipped motor controllers and battery systems, and I have been the human at the bench this page describes. If testing your firmware still means a person and an afternoon, I want 15 minutes.