Checking Logic Analyzer Thresholds Before Trusting a Decode

A protocol decoder interprets the digital transitions delivered by its acquisition hardware. If the input threshold is inappropriate, a correct decoder can produce misleading bytes or extra edges. Establish how the analyzer converts voltage into logic before using a decode to diagnose the board.

Separate recognition from input tolerance

Saleae’s supported voltage documentation distinguishes digital recognition thresholds from over-voltage limits. It also describes model-dependent threshold options, including settings shared across channels. The fact that an input can tolerate a voltage does not mean that every logic swing is recognized correctly.

Identify the analyzer model and the electrical standard of each observed signal. Check whether mixed-voltage buses can be acquired simultaneously with the available thresholds. Do not assume that a software label such as ‘3.3 V’ describes the exact switching threshold or permits connection to any interface with a similar nominal voltage.

Confirm the analog conditions first

Use an appropriate voltage measurement to check high and low levels, rise and fall behavior, and the reference connection. A digital trace suppresses this information. A slowly crossing or noisy signal can produce a sequence of interpreted transitions that looks like a protocol problem.

For example, an apparent extra clock edge could come from the circuit, the analyzer’s threshold behavior, or the connection. Capture the analog waveform at the relevant location to distinguish those possibilities before changing firmware timing.

Review capture and decoder settings together

• Select a sample rate capable of resolving the events being investigated.
• Confirm channel mapping, polarity, bit order, and protocol timing options.
• Record any glitch filtering and understand which events it removes.
• Capture enough activity before and after the error to establish context.
• Compare decoded data with raw digital transitions at the disputed transaction.

A glitch filter can make a trace easier to decode, but it can also hide a real narrow event. Keep the original capture and document filtered views separately. Increasing sample rate does not repair an incorrect threshold or an electrically unsuitable connection.

Save the capture configuration, analyzer model, wiring photograph, and expected transaction alongside the result. A successful decode demonstrates that the analyzer interpreted a sequence under those conditions; it does not independently prove signal-integrity margin at the receiving device. Use it together with electrical and timing measurements when that margin matters. This distinction makes protocol debugging faster because each instrument is asked a question its measurement can actually answer.

Label the tested receiving device as well as the observed signal, especially when several devices share a bus with different electrical limits.