Eliminating decoder spikes in counter systems A dependable technique for suppressing short, unwanted pulses (glitches) on decoded outputs is commonly called what?

Introduction / Context:
When decoding counter outputs, asynchronous transitions can momentarily produce incorrect decode combinations, observed as narrow spikes. Designers routinely mitigate these glitches to prevent false triggering of actuators, displays, or logic that follows.

Given Data / Assumptions:

• We are decoding a multi-bit counter output with combinational logic.
• Due to ripple delays, intermediate non-valid codes can appear during transitions.
• Goal: prevent downstream circuits from reacting to those brief spikes.

Concept / Approach:
“Strobing” is the practice of gating the decoded output with a timing signal that only enables observation when the counter outputs are known to be stable. Typically, the strobe is derived from the clock or from a registered (synchronous) version of the decode. By ensuring the enable window occurs after propagation delays settle, spikes are masked.

Step-by-Step Solution:
Identify when outputs are valid relative to the clock edge.Generate a strobe/enable pulse in the valid window.AND the decoded lines with the strobe so only stable data passes.

Verification / Alternative check:
Scope measurements show spikes disappear at the gated node, while the raw decode still exhibits hazards. Synchronous registering of the decode is an equivalent approach.

Why Other Options Are Wrong:
“Feeding,” “wagging,” and “waving” are not recognized techniques in this context.

Common Pitfalls:
Setting the strobe window too early (before signals settle); forgetting to account for temperature and process variations in propagation delays.

Final Answer:
strobing