Foundational theory

Compliance & Coverage Plan is a core topic in Protocol Verification & Compliance. compliance maps spec requirements to tests, assertions, coverage bins, exclusions, and signed waivers. Senior engineers treat it as a contract problem: each boundary must preserve transaction identity, ordering rules, and forward progress under backpressure.

Core concepts explained

• compliance maps spec requirements to tests, assertions, coverage bins, exclusions, and signed waivers.

• Primary metric: spec feature coverage, compliance pass rate, waiver count

• Primary artifact: requirement trace matrix, coverage dashboard, waiver log

• Owners: verification lead, IP owner, signoff owner

• Layer model: software intent → transaction → channel/link → physical/timing

• Debug posture: find the first deviation, not the loudest timeout

Why this matters in real chips

In silicon integration, Compliance & Coverage Plan failures appear as hung transactions, corrupted data, bandwidth cliffs, or bring-up stalls. Verification proves the contract holds under legal and stressful traffic mixes. Without mechanism-first analysis, teams burn weeks widening buses or blaming firmware.

Mental model

COMPLIANCE TRACE MATRIX

spec clause ──> test(s) ──> assertion(s) ──> coverage bin ──> status
  4.2.1          t_axi_07     a_resp_ok        cov_resp        PASS
  4.3.5          t_axi_12     a_order          cov_order       WAIVED (id=W3)
  4.4.0          (none)        (none)           (none)          GAP  <- find these

A gap row is the most valuable output of the plan.

Worked intuition

1. Name the workload or traffic class exercising Compliance & Coverage Plan.

2. Open spec feature coverage, compliance pass rate, waiver count and identify the failing cluster (p99 often matters more than average).

3. Tag transaction identity: ID, address, endpoint, lane, or cache line.

4. Map the symptom to protocol layer: transaction, link, or physical.

5. Collect requirement trace matrix, coverage dashboard, waiver log and align timestamp with VIP or analyzer view.

6. Reduce to smallest legal/illegal sequence that reproduces the bug.

7. Propose one bounded fix and list compliance + product regressions.

Common misconceptions

• Handshake activity implies the transaction is legal.

• Peak interface width equals useful payload bandwidth.

• A VIP pass guarantees integrated-system correctness.

• Software timeouts always mean the PHY or link is broken.

• More buffering fixes ordering or coherence bugs without analysis.

Visual reinforcement

Requirement-to-coverage trace

COMPLIANCE TRACE MATRIX

spec clause ──> test(s) ──> assertion(s) ──> coverage bin ──> status
  4.2.1          t_axi_07     a_resp_ok        cov_resp        PASS
  4.3.5          t_axi_12     a_order          cov_order       WAIVED (id=W3)
  4.4.0          (none)        (none)           (none)          GAP  <- find these

A gap row is the most valuable output of the plan.

Layer responsibilities

LAYER RESPONSIBILITY — Compliance & Coverage Plan

layer          owns                         common failure
-----------    --------------------------   -----------------------
software       intent, ordering needs       wrong assumption
transaction    id/addr/len/attributes       ordering / outstanding
link/channel   handshake, credits, retry    backpressure / deadlock
physical       clock/reset/lanes/PHY        timing / training / SI
observability  waveform/log/counter         missing evidence

Protocol deep dive

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

Concept diagram

VERIFICATION CLOSURE LOOP

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

Metric graph

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.

Theory reinforcement

Verification proves the contract holds under legal and stressful traffic mixes.