Connect the Debug Probe Reference to the Correct Target I/O Domain

A debug connector can carry a target-voltage reference without supplying power to the board. Confusing those functions can produce a dead target, incorrect logic levels or an unintended power path. Review the probe, adapter and board connector together before treating a connection failure as a firmware problem.

Separate reference from supply

SEGGER’s VTref documentation explains that the target provides its I/O reference voltage so the probe can adapt interface levels. VTref is not the target power output. Some probe arrangements have separate power features, which require their own connector and configuration review.

Label the board connector pins by function and voltage domain. Identify the supply associated with the target’s debug I/O, not merely the most convenient nearby rail. Check any adapter pin mapping rather than assuming that a cable with the right physical connector preserves every signal.

Follow the power states

List normal operation, target off, probe connected first and any mode that switches the debug I/O supply. Determine what voltage the probe sees in each state and whether the target pins are powered. Include onboard debuggers or test fixtures that may also connect to the same interface.

If the design uses a probe’s fixed-reference option, document the exact supported configuration and target voltage assumptions. A fixed setting can be useful in a controlled fixture, but it removes automatic evidence that the connected target is operating at the expected level.

Verify the connection at the connector

Measure the reference relative to the connector ground and compare it with the target I/O domain. Inspect continuity, orientation and ground connection before changing software settings. Record both the probe’s reported reference and the measured voltage when they disagree.

Then inspect clock and data waveforms with the intended cable and interface speed. An incorrect reference can be one cause of failure, but correcting it does not prove reset wiring, target mode or signal integrity is correct. Continue with a defined interface checklist rather than changing several unrelated settings at once.

Make production behavior explicit

For a programming fixture, state who powers the target, when the probe may drive signals and what prevents two supplies from conflicting. Verify the exact fixture adapter used on the line. A development bench powered through a separate USB connector may conceal a missing production power connection.

Retain the connector map, target voltage domain, probe configuration and power sequence with the hardware release. If a processor revision changes its debug I/O supply, revisit the reference connection. This keeps a simple voltage-sense pin from becoming an undocumented assumption shared between hardware, firmware and the programming fixture.