Board Bring-Up, Test, and Debug
Board bring-up is the first controlled power-up and validation of a new PCB. Good bring-up is methodical: inspect first, limit energy, verify rails, check clocks and resets, test interfaces one at a time, and record every observation.
Learning Objectives
By the end of this lesson, you should be able to plan a bring-up sequence, power a board safely, verify supplies and clocks, isolate faults, use test points effectively, and turn bring-up learning into production tests.
Before Power
Inspect the assembled board:
- correct board revision;
- correct component orientation;
- no solder bridges or missing parts;
- connector pinout and polarity;
- resistance from each power rail to ground;
- jumpers and boot strapping options;
- current limit and expected current.
Do not apply full power to an unknown board without current limiting.
First Power-Up
Use a bench supply with current limit. Start with a conservative limit based on the expected idle current.
[
P=VI
]
If a 5 V board unexpectedly draws 1 A:
[
P=5\text{ V}\times 1\text{ A}=5\text{ W}
]
That can overheat small parts quickly. Stop and investigate.
Bring-Up Flow
Rail, Clock, and Reset Checks
Measure at the load, not only at the regulator. Check:
- rail voltage and ripple;
- startup sequence;
- reset pin timing;
- oscillator startup;
- boot mode pins;
- regulator temperature;
- current in sleep and active modes.
For ripple or fast edges, use a short probe ground spring to avoid measurement artifacts.
Interface Testing
Test one interface at a time. Start with simple checks:
- UART console or SWD/JTAG connection;
- I2C scan;
- SPI read of known device ID;
- GPIO toggle;
- ADC reading of a known voltage;
- communication loopback if available.
Use firmware that is intentionally small and observable.
Fault Isolation
When something fails, reduce variables:
- remove optional loads;
- isolate rails with jumpers or zero-ohm links;
- compare known-good and failing boards;
- inject a known signal;
- inspect with microscope and thermal camera;
- read current before and after each change.
Do not keep increasing current limit to "push through" a fault.
Production Test Planning
Bring-up should produce reusable tests:
- power rail acceptance limits;
- firmware programming method;
- serial number or calibration write;
- boundary or fixture tests;
- pass/fail logs;
- known fault symptoms and repair notes.
Design-for-test decisions are cheapest before the next PCB revision.
Practical Review Checklist
- Current-limited supply ready.
- Rail-to-ground resistance recorded.
- Test firmware prepared.
- Oscilloscope and DMM probes suitable.
- Expected voltages, currents, and clocks listed.
- Failure log template ready.
- Production test improvements captured.
Common Mistakes
- Powering the board before visual inspection.
- Measuring only regulator outputs and not load pins.
- Debugging firmware before reset, clock, and power are proven.
- Changing multiple variables at once.
- Ignoring hot parts because the board still runs.
Summary
Bring-up is controlled evidence gathering. Inspect, limit current, verify rails, clocks, resets, firmware access, and interfaces in order. Record failures, isolate them systematically, and convert lessons into design fixes and production tests.
Further Reading
- Elecia White, "Making Embedded Systems," debugging and bring-up chapters.
- Texas Instruments, "Power Supply Measurement and Probing."
- IPC-A-610 acceptability of electronic assemblies.