Protocol Waveform Debug: Interview Drills

PROMPT
You see debug turnaround time, root-cause classification, rerun pass rate on Protocol Waveform Debug. Walk through root cause and fix.

STRONG ANSWER
1. Names the layer and transaction identity.
2. Explains waveform debug reconstructs transaction intent from signals, monitors, logs, and spec rules in timestamp order.
3. Requests annotated waveform, transaction timeline, root-cause note.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to widening the interface, increasing FIFO depth, or blaming firmware without evidence.

RECONSTRUCT INTENT FROM SIGNALS

step 1: find first anomaly timestamp (T0)
step 2: scroll BACK to the request that started it
step 3: annotate id/addr on every related signal
step 4: mark where progress should have happened but did not
step 5: compare with the spec timing for that exact transaction

T-2   T-1   T0(bad)   T+1
 |     |      |         |
req  grant  (no resp)  timeout
        ^ root cause lives here, not at the timeout

ROOT-CAUSE TREE — Protocol Waveform Debug

debug turnaround time, root-cause classification, rerun pass rate looks wrong
        |
   reproducible?
     /        \
   no          yes
   |            |
 flaky env   same first transaction every time?
 / seed         /            \
              yes             no
               |               |
        protocol rule     timing/reset/PVT
        or config bug     or load-dependent

VERIFICATION CLOSURE LOOP

spec clause -> test -> assertion -> coverage -> waiver -> signoff
                  ^                           |
                  +--------- gap found --------+

COVERAGE vs ESCAPE RATE

escapes
  |*
  | *
  |  *
  |   **  <- knee: more random helps
  |     ****
  +----------------> constrained-random depth