Interface Protocols · All levels

Scoreboard & Checker Strategy: Comparison Matrix

Comparison Matrix for Scoreboard & Checker Strategy.

Comparison matrix

VIP depth, scoreboard keys, and compliance mapping define escape rate vs schedule.

diagram

+------------------+----------------+----------------+----------------+
| Approach         | Strength       | Weakness       | Best when      |
+------------------+----------------+----------------+----------------+
| Baseline         | known, signed  | may miss peak  | shipping SKU   |
| More buffer      | absorbs latency | area, deadlock | DMA-heavy      |
| Wider bus        | peak BW up     | timing, power  | memory bound   |
| SW contract      | cheap silicon  | driver burden  | fixed platform |
+------------------+----------------+----------------+----------------+

When to choose each approach

Pick baseline when schedule and risk dominate
Pick buffering only after proving backpressure is the limiter
Pick width only after payload efficiency analysis
Pick software contract when hardware change is too expensive

Interview traps

Comparing peak spec numbers across protocols
Ignoring bridge and firmware in the comparison
One-size-fits-all answer in interviews

Evidence comparison

diagram

COMPLIANCE / DEBUG MATRIX — Scoreboard & Checker Strategy

+-------------------+------------------------+--------------------------+-------------------------+
| Evidence           | Tells you              | Does not prove           | Next action             |
+-------------------+------------------------+--------------------------+-------------------------+
| Waveform           | signal-level sequence  | full system intent       | map to transaction log  |
| VIP transaction    | spec-level behavior    | RTL micro-cause          | correlate timestamp     |
| Counter / PMU      | aggregate symptom      | single failing packet    | isolate traffic class   |
| Firmware log       | software-visible flow  | electrical/link health   | compare with hardware   |
| Analyzer capture   | external protocol view | internal reset/config    | align with RTL trace    |
+-------------------+------------------------+--------------------------+-------------------------+

Protocol deep dive

Verification closes the gap between 'works in directed test' and 'legal under all stressed traffic'.

Concept diagram

diagram

VERIFICATION CLOSURE LOOP

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

Metric graph

diagram

COVERAGE vs ESCAPE RATE

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

Metrics and artifacts to collect

compliance pass rate
coverage closure
scoreboard mismatch rate
assertion fire count
waiver log

Mini case study

Block passed VIP compliance but chip failed: system test omitted cross-master ID reuse through a bridge. Scoreboard key did not include upstream port ID.

Debug branches

If VIP pass but silicon fail, check integration assumptions.
If scoreboard noisy, fix key (ID+port+addr).
If coverage plateau, add compliance gap analysis not more repeats.

Senior review question

Ask: what is the first transaction that deviates, and which spec rule does it test?

Key takeaways

Connect every protocol claim to a transaction identity and measurable metric.
Store the artifact (waveform, log, counter) next to every signoff decision.

Common pitfalls

Debugging timeouts without finding the first bad transaction.
Quoting peak bus width without payload efficiency and retry overhead.
Treating VIP compliance as a substitute for system integration replay.

Principal review addendum

Re-read Scoreboard & Checker Strategy against one concrete product workload, not a synthetic directed test.

scoreboards correlate requests and responses while assertions check local temporal rules and illegal combinations.

Practice this lesson