Boardview and Schematics: How to Trace a Circuit on a Board

Without the schematic, a location alone may not tell you the signal's role. Without a boardview, finding a safe point on a dense board can take much longer. Without a measurement, the documents describe the intended circuit, not the fault.

Always match the document to the board number and revision. A similar model name is not enough: pin assignments and component population can change between revisions.

A boardview file is board-specific data. Depending on its format, it can include component locations, pin positions, net names and connections. A reader uses that data to highlight a component or the accessible points belonging to a selected net.

Search for a reference designator to find a component. Search for a net name to find the pins and pads connected to that net. Check the selected board side and orientation before placing a probe. Not every file includes every via or test point.

OpenBoardView is an open-source reader; commercial tools also exist. Format support and schematic integration vary. The reader is a map, not a fault detector: it cannot establish that a component is defective merely because you selected it.

On a sparse, simple board, a schematic, visual inspection and power-off continuity checks may be enough to follow a connection. On a dense phone or laptop board, hidden traces and closely spaced components make a matching boardview much more useful.

Boardview availability is not a requirement for learning the method. Start with an openly documented development board: identify a circuit in the schematic, find its physical components and compare a measured value with the expected state. The Arduino UNO reference schematic below is one example of an openly available circuit document. It is not a boardview file for a phone or laptop.

1. Convert the symptom into a testable question. 'It does not charge' is a symptom. 'Is the regulator enable input asserted in this operating state?' identifies a signal, a condition and a decision.

2. Find the circuit in the schematic. Identify the net, its source and its loads. Establish whether it carries power, a control signal or data. Use the relevant component documentation for thresholds and timing; the net name alone does not supply them.

3. Locate accessible points. Use the boardview to find the same net on the correct board revision. Check the physical board against the map before touching it.

4. Choose the appropriate instrument and state. Resistance, continuity and diode checks require a de-energized circuit with stored charge addressed. Voltage and waveform measurements require a controlled powered test. Do not interpret those modes interchangeably.

5. Compare source and load. A difference can narrow the search, but account for any series component, switch or operating-state change between the points. A low reading alone does not prove an open connection or a failed IC.

Prefer a clearly identified test point with room for the probe. An accessible passive-component pad or via may be suitable if it belongs to the same net and the probe can reach it without slipping. The practical order depends on size, spacing, coating and access; a tiny exposed via is not automatically safer than a large resistor pad.

Treat a fine-pitch IC pin as a last resort when a safer point can provide the same information. Stabilize the board and use an appropriate probe. Bridging adjacent pins on a powered board can create a new fault.

For a waveform, location is only part of the problem. Probe capacitance and the ground connection can change what you see. Select the probe and grounding arrangement for the signal being measured.

Open hardware projects often publish schematics and design files. Consumer-device documentation may be restricted or unavailable. Use files you are entitled to access; an open-source reader does not grant permission to redistribute someone else's board files.

For each finding, record the model and board revision, net, test point, instrument mode, probe polarity, power state, expected value and actual reading. If a reference board was used, identify its revision and condition. A record that another technician can reproduce is more useful than a screenshot with an unexplained number.