An electronic PCB circuit is the combined behavior of its components, interconnections, power supply and operating environment. When a new assembly fails, start by finding which requirement is not met. Replacing parts at random usually loses information and can introduce another fault.
Prepare a bring-up record before applying power
Identify the board revision, BOM variant, firmware version and any known rework. Gather the schematic, assembly drawing and relevant component documentation. Define expected supply rails and the order in which major functions should become available.
Choose a supply and current limit appropriate to the design. Check instrument and probe ratings for the circuit being measured. A bench setup suitable for a small low-voltage board is not automatically suitable for a high-energy or mains-connected system.
Separate observations from hypotheses
| Observation | Next question |
|---|---|
| No expected input voltage | Is the source, cable or connector delivering it? |
| Input present but rail absent | Are enable conditions, load and regulator connections correct? |
| Rails present but no activity | Are reset, clocks and configuration conditions satisfied? |
| One interface fails | Is the problem at the local circuit, connection or external device? |
| Failure under load | What changes electrically or thermally when the load is applied? |
Write measured values and conditions beside the hypothesis. A statement such as the controller is bad is not evidence. A repeatable reset waveform or missing supply rail is a useful observation that can guide the next check.
Include the probe location and reference connection in measurement notes. Two measurements described only as output voltage may actually refer to different nodes or different points in the startup sequence.
Change one variable at a time
- Inspect assembly and component orientation.
- Check the relevant connections with power removed where appropriate.
- Verify supplies and startup conditions.
- Exercise one functional block with a known input.
- Compare the response with the expected behavior.
- Record any modification and repeat the same test.
When comparing a working and failing unit, keep the setup and operating state consistent. Differences in firmware, jumpers or external cables can imitate a board fault. Preserve the original failing state long enough to understand it.
Turn findings into a controlled revision
Distinguish assembly defects, component substitutions, design errors and test-setup problems. Each requires a different corrective action. A wire added during debugging may demonstrate a cause, but its routing and reliability still need review before becoming a production change.
Update the schematic, layout, BOM and test instructions together. The schematic review guide helps catch missing design intent, while the testing overview supports a repeatable acceptance process for later builds.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist