What it actually takes to get your board onto the Oracova bench: the hardware, the documents, and the bring-up. Two paths, depending on whether you already have working firmware.
A custom DUT board is made for your microcontroller and goes onto the Oracova base board. DUT designs are open source.
Plays your sensors and loads protocol-exact and runs the physics models. The world responds like the product's world does.
DAC and ADC modules come in different resolutions and speeds; you pick the ones your signals need. Unusual signal? A module can be built for it.
Built for your part, every pin routed to the base board. Your code runs on your real silicon, not a substitute part. The probe flashes, resets, and inspects the target while it runs.
Benches are cheap to replicate. One per PR, one per agent, as many as your team runs in parallel.
Next is collecting information: your actual PCB, its schematics, datasheets, pin assignments, and a description of how the product works. This is what the bench will stand in for.
Now the world comes up. An AI agent does the work, with your confirmation along the way.
On either path, expect some questions about your hardware and its physics, or documentation that answers them. The agent asks, it does not guess.
The world rarely starts from zero. Common peripherals, a gyro, an LCD, a hall encoder, come as validated models from Oracova's open-source marketplace, already proven against real firmware on other benches. The AI builds what is unique to your product and pulls the rest. And what you build, you can contribute back.
Bring your schematic to the call. 15 minutes, no deck.
Book 15 minutes