DenseChip

CDC / RDC · All levels

Multi-bit Crossing Strategies: Step-by-Step Walkthrough

Step-by-Step Walkthrough for Multi-bit Crossing Strategies.

Step-by-step analysis walkthrough

Use this sequence when owning Multi-bit Crossing Strategies in a signoff review.

  1. Inspect warning class and severity.

  2. Trace crossing endpoints and domains.

  3. Check protocol/reset assumptions against spec.

  4. Review synchronizer or FIFO implementation detail.

  5. Run focused assertion or formal check.

  6. Draft fix options with risk and schedule impact.

  7. Execute regression and publish closure memo.

Artifacts to collect

  • strategy decision matrix, interface timing contract, verification plan

  • crossing inventory

  • waiver board notes

  • regression report

Decision memo template

diagram
CDC/RDC DECISION MEMO — Multi-bit Crossing Strategies
risk class:
mechanism:
evidence:
fix/waiver:
owners: architecture owner, RTL owner, CDC lead

Reference visuals

Strategy matrix

diagram
bundle+valid/ready  : moderate latency, strong coherency
async FIFO         : high robustness, area cost
source strobe      : throughput friendly, timing contract heavy
token protocol     : explicit ordering, more control logic

CDC/RDC deep dive

Reconvergence failures are timing + logic coupling hazards.

Concept diagram

diagram
RECONVERGENCE

branch A sync --                 -> merge logic -> illegal combination window
branch B sync --/

Metric graph

diagram
HAZARD REPRODUCTION RATE

before fix: 1/2000 runs
after fix: 0/100000 runs

Reports and artifacts

  • reconvergence warnings

  • gray transition checks

  • hazard replay traces

  • multi-bit strategy map

Mini case study

Gray pointer was legal, but downstream merge decoded mixed-era values during burst stress.

Debug branches

  • Trace fanin cones

  • align event windows

  • verify decode assumptions

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

Key takeaways

  • State crossing class, assumptions, and owner with every issue.

  • Run structural and dynamic regressions after each fix.

Common pitfalls

  • Treating all warnings as equivalent risk.

  • Waiving issues without containment evidence.

  • Skipping reset and reconvergence stress after CDC fixes.

Principal CDC/RDC review addendum

Bundled-data handshakes, FIFOs, source-synchronous strobes, and encoded protocols each trade latency, area, and proof complexity.

Metric: coherency guarantee coverage, data corruption incidents, protocol overhead

Practice this lesson