One falsifiable boundary at a time
PCB Bring-Up and Debugging System
Move from unpowered inspection through controlled first power, rails, clocks, reset, programming, interfaces, load, and a reproducible baseline.
Short answer
Bring-up is an ordered experiment: establish board identity, inspect without power, bound fault energy, verify the power tree, prove reset and clocks, load minimal firmware, and add one interface or load at a time. If several variables change between observations, the bench is producing stories instead of evidence.
Design sequence
Step 1
Freeze identity and expectations
Record board, schematic, BOM, assembly variant, firmware, expected rails, expected current states, and the first planned observation.
Step 2
Inspect and measure unpowered
Find bridges, orientation errors, footprint mismatches, connector mistakes, and unexplained low-resistance rails before giving the fault energy.
Step 3
Apply controlled power
Use the designed input voltage and a justified current limit while watching current, the input, the first critical rail, and unexpected heat.
Step 4
Advance by subsystem
Prove rails, reset, straps, clocks, programming, minimal firmware, one interface, and then load. Preserve the last known-good boundary.
Stop conditions
- Stop immediately for unexplained current, collapsed input, unexpected heat, smoke, smell, unstable rails, or a mismatch between the physical board and its source files.
- Stop changing variables when a subsystem fails. Choose one measurement that can falsify the next hypothesis.
Choose each subsystem
Voltage Regulators
Linear regulators and references: dropout, stability requirements, quiescent current, and thermal limits.
Buck Converters
Step-down switchers: real continuous-current ratings, external diode requirements, and layout-sensitive nodes.
Microcontrollers
MCUs and MCU modules: minimal circuits, strapping and boot pins, clock requirements, and the supply gotchas that cause field failures.
Interface ICs
USB bridges, transceivers, expanders, and level shifters: driver situations, reference pins, and bus speed limits.
Sensors
Environmental, motion, and current sensors: address pins, self-heating, counterfeit detection, and interface modes.
Motor Drivers
H-bridges and stepper drivers: current limits vs heatsinking, decay modes, and protection.
Verified part guides
These pages establish exact part boundaries and datasheet-backed constraints. They are examples and design references, not a universal BOM.
- INA219Bidirectional I2C current, voltage, and power monitor for rails up to 26 V.
- AP63203WU-7Wide-input 3.8–32 V, 2 A synchronous buck converter with fixed 3.3 V output, 1.1 MHz switching, integrated MOSFETs, and enhanced EMI reduction.
- LM1117-3.3Fixed 3.3 V, 800 mA low-dropout regulator in the classic SOT-223 1117 footprint.
- ATmega328P8-bit AVR MCU with 32 KB flash; Arduino Uno chip; also PDIP-28.
- CH340CUSB-to-UART bridge with internal oscillator; dominant on budget dev boards.
- CP2102NUSB-to-UART bridge with internal oscillator and 3 Mbaud throughput; 3 package options down to 3x3 mm QFN.
Take it to the bench
Questions to take into PCBWiki
- What is the next falsifiable measurement after first power hits current limit?
- My rails are correct but programming fails—what boundary should I test next?