# PCB bring-up checklist: from first power-on to a tested board

> Bring-up is the work of taking a newly assembled board from "never powered" to "known to work". This checklist gives the order most hardware teams follow, and what to write down at each step.

## What is PCB bring-up?

PCB bring-up is the first power-on and step-by-step check of a newly assembled printed circuit board. You power the board carefully, confirm each power rail, then clocks, reset, programming access and each interface in turn. The goal is to find design and assembly faults early, one stage at a time, so that a fault in one stage does not damage the next.

## 1. Before the boards arrive

- Write the test plan. For every power rail, write the expected voltage, the allowed range, and the test point where you will measure it.
- List the order in which rails should come up, and the expected state of each enable, power-good and reset signal.
- Print or open the schematic, the layout and the assembly drawing, with test points marked.
- Set up the bench: a current-limited power supply, a multimeter, an oscilloscope with suitable probes, and the programmer or debugger for your processor.
- Have test firmware ready. A build that blinks an LED and prints over a serial port is enough to start.
- Decide how you will record results, so that every unit is measured and logged the same way.

## 2. Inspect before power

- Check the board against the assembly drawing: every part placed, none rotated, polarized parts the right way round.
- Look at fine-pitch parts and connectors under magnification for solder bridges and open joints.
- Check that no-fit parts are really not fitted, and that any rework is clean.
- Note the serial number of the unit. Results are only useful if you know which board they came from.

## 3. Check for shorts with the power off

- Measure the resistance from each power rail to ground with a multimeter.
- A reading near zero ohms on a rail usually means a short. Find it before applying power.
- Compare readings between units. A board that reads very differently from the others on one rail deserves a closer look.
- Check continuity on any net you have a specific reason to doubt, such as a reworked joint.

## 4. First power-on

- Use a bench supply with a current limit. Set the input voltage, and set the limit a little above the current you expect.
- Switch on and watch the current. If the supply hits the limit, switch off and investigate.
- If the design allows, power one stage at a time, for example by leaving jumpers or zero-ohm links open.
- Feel for hot parts, or use a thermal camera. A part that is hot within seconds is a fault.

## 5. Verify every rail

- Measure each rail at its test point and compare it with the expected range.
- Work in the order the rails come up. A wrong upstream rail explains many downstream faults.
- Check ripple and noise with an oscilloscope on the rails that feed sensitive parts.
- Capture the power-up sequence: the order and timing of the rails, power-good signals and reset.

## 6. Clocks and reset

- Check that each oscillator runs, at the right frequency and amplitude.
- Check that reset is held during power-up and released once the rails are stable.
- Check the level of any boot-mode or strap pins at the moment reset is released.

## 7. Programming and debug access

- Connect the debugger and read the device ID. This confirms power, clock, reset and the debug wiring in one step.
- Program the test firmware and confirm it runs.
- For programmable logic, load a simple bitstream and confirm configuration completes.

## 8. Bring up interfaces one at a time

- Low-speed buses first: confirm every device answers on I2C, SPI and UART.
- Memory: run a read and write test.
- High-speed links (for example MIPI, USB, Ethernet, LVDS): check the link trains, then check signal quality with an eye diagram.
- Analog paths: inject a known signal and compare the measured result.
- Radios: check output power and frequency into a test port.
- Outputs that drive loads, such as motor phases: start with a current limit and a small load.

## 9. Test under real conditions

- Run the board at full load and watch the rails for droop and noise.
- Apply load steps and check that the regulators recover.
- Let the board warm up and repeat the key measurements.

## 10. Record results and make them repeatable

- For every test, record the unit, the measured value, the limit and the result.
- Compare units. A value that is in range but far from the other boards is worth understanding.
- Turn the checks that found problems into a repeatable test for the next units, the next revision and production.

## How does Agonic automate this?

Most of this checklist is the same set of measurements on every unit, and doing them by hand is slow and hard to repeat exactly. Agonic builds a custom interposer board and probe dock for each revision of your board. Your bench instruments plug in once, and an AI agent runs the tests on every unit and writes the verification report, with the measured value, the limit and the result for each test.

The kit is built while your PCB is in fab, so it is ready the day your boards arrive. A typical kit is $1,925 before coupons. See [Pricing](https://agonicai.com/pricing), the [comparison with other test methods](https://agonicai.com/compare), or get an [instant quote](https://agonicai.com/#quote).

---

Source: https://agonicai.com/pcb-bring-up-checklist · Updated 2026-11-15 · Agonic AI Inc., San Francisco, California, USA · engineering@agonicai.com
