Hardware Bringup: A Systematic Approach to First Power-On
The first time you power on a new board is the moment of truth. Here's the methodical bringup sequence we use to diagnose issues fast and protect expensive prototypes.
There is a specific kind of dread that accompanies pressing the power button on a new PCB for the first time. You've spent weeks on the design, the board just came back from the fab, the BOM is assembled — and now you're about to find out whether it works, whether something is subtly wrong, or whether something is catastrophically wrong and you just released the magic smoke from an expensive prototype.
The difference between an engineer who dreads bringup and one who approaches it calmly is a methodology. A systematic bringup procedure protects your hardware, surfaces problems quickly, and gives you the data you need to debug efficiently. Here's the sequence we use at HarQuinn Tech.
Before You Power On
Visual Inspection and Continuity Test
Before connecting any power, do a thorough visual inspection under magnification — check for solder bridges on fine-pitch components, missing components, tombstoned passives, and cold solder joints on BGAs or QFNs. Then, with a multimeter, verify continuity from each power input pin to its expected rail, and check resistance from each power rail to ground. A dead short to ground before power-on saves you from destroying your board.
Set Up Current-Limited Power Supply
Use a bench power supply with current limiting set to 10–20% above the expected idle current draw for your board. This is your safety net — if there's a short or a component drawing catastrophic current, the supply current-limits before damage occurs. Do not use an unregulated wall adapter or a battery for first power-on. A bench supply with current limiting is non-negotiable.
The Power-On Sequence
Power On with No Load — Check Idle Current
Apply power and immediately check the current reading on your bench supply. Compare to your pre-calculated idle current estimate. A significantly higher current than expected indicates a problem — stop, power off, and investigate before proceeding. Common causes: reversed component, solder bridge, wrong component value in a bias network, or a leaky protection diode.
Verify All Power Rails
With power on, measure every voltage rail on your board against the expected value. Work from input to output — check the main supply rail first, then each downstream regulator output. A rail that's missing or significantly off tells you exactly which section of the power tree to debug. Don't proceed to loading the board until all rails are verified.
Check Clocks and Reset
With rails verified, check that your main oscillator or crystal is running — probe the clock output with a scope. Verify that reset signals are de-asserting correctly and at the right time after power-up. Many processors and FPGAs won't boot at all if the reset sequence is wrong, and they'll give you no indication why. Catching a missing clock or stuck-assert reset at this stage saves hours of debug.
Bring Up Communication Interfaces
Once your processor or FPGA is running, bring up your communication interfaces one at a time — UART first (lowest risk), then I2C, SPI, and finally any high-speed interfaces. Talk to each peripheral individually and verify it responds correctly before proceeding to the next. This methodical approach isolates problems to a specific interface rather than leaving you with a system that doesn't work and no idea why.
"Bringup is not a test — it's a diagnostic procedure. The goal isn't to find out if the board works. It's to find out what specifically isn't working, as quickly as possible, with the least risk to the hardware."
When Something Goes Wrong
Something will go wrong on a first prototype. This is not a failure of the design process — it's the expected outcome of building complex hardware for the first time. The question is how quickly you can identify and resolve the issue. Keep a debug log: record what you tested, what you measured, and what the result was. Systematic documentation during bringup turns a confusing failure into a traceable root cause.
At HarQuinn Tech, we support hardware bringup as part of our engineering services — from pre-bringup design review to hands-on debug support for complex prototype issues. If you're bringing up a new board and hitting walls, reach out.
Stuck on a Hardware Bringup?
Our engineering team provides hands-on bringup support and prototype debug services.