Board bring-up

From your PCB to verdicts.

What it takes to get your board onto the Oracova bench. Two paths, depending on whether you already have working firmware.

STEP 1

The documents

This is what the bench will stand in for.

your actual PCB schematics datasheets pin assignments how the product works DUT board PCB, if you have one
STEP 2

The hardware

From your documents, a custom DUT board is designed for your microcontroller and goes onto Augur One (in fabrication, first article pending). Designs for popular parts are published open source.

Oracova base board

The world, in real time

Plays your sensors and loads, protocol-exact, and runs the physics models in real time.

Analog modules

Four channels per slot

Each of the 10 slots takes a high-speed or a low-speed module; populate only the slots your signals need. Unusual signals get a custom module.

Custom DUT board + debug probe

Your microcontroller's seat

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 it live.

STEP 3

The bring-up

An AI agent does the work, with your confirmation along the way; it asks about your hardware and its physics rather than guessing. How long depends on your board: we scope it, with a number, on the call.

If you have working firmware

01Read the source The AI learns the world your firmware expects: peripherals, protocols, what it drives and senses.
02Write the world It writes the I/O behavior and the physics models.
03Run and compare Your unmodified binary runs on the DUT, the debug probe watching internal state, behavior compared against the field.
04Iterate to golden Until your firmware runs on the bench the way it runs in the product. That run is recorded as golden; the suite builds on it.

If you do not have working firmware yet

01Peripheral by peripheral The bench and the firmware grow together, interface by interface.
02Driver + world as a pair The firmware driver on the DUT and its counterpart in the world, brought up as a pair.
03Pass before proceed Each peripheral passes on the bench before the next one is added.
04The suite is the record By the time the firmware is whole, the regression suite already exists.
The world does not start from zero
gateware buses · capture · fault injection · plant framework

Already proven on Oracova development hardware. Only your product's physics is new, and it is built on that foundation, not from a blank page.

Where the boundary sits
Emulated

Everything your MCU senses and drives

Digital buses connect directly; analog signals go through analog modules built for your board.

GPIO · PWM · UART · I2C · SPI · CAN
Not emulated

Your power stage

High voltage and high current stay off the bench. Your firmware still sees the same signals it would see in the product.

Running today

The closed loop runs on real silicon, on development hardware

See flight controller in loop →

Want to walk through it on your board?

Bring your schematic. 15 minutes, no deck.

Email your schematic