RDC Methodology: Theory Deep Dive

Foundational theory

RDC Methodology anchors RDC Signoff. RDC methodology treats reset behavior as a first-class asynchronous interface requiring intent capture, structural checks, and targeted dynamic proof. Senior signoff discussions tie every warning to mechanism class, operational mode, and risk containment evidence.

Core concepts explained

• RDC methodology treats reset behavior as a first-class asynchronous interface requiring intent capture, structural checks, and targeted dynamic proof.

• Primary metric: reset-domain hazard coverage, unresolved RDC severity count, closure quality

• Primary artifact: RDC methodology guide, rule-set config, hazard taxonomy

• Owners: RDC lead, methodology owner, verification lead

• Distinguish structural cleanliness from functional correctness.

• Tie every waiver to silicon-risk framing and expiry.

Why this matters at signoff

At tapeout, unresolved CDC/RDC issues become latent reliability bugs. RDC signoff makes reset behavior measurable, reviewable, and reproducible.

Mental model

intent capture -> structural run -> dynamic proof
        -> waiver board -> milestone gate -> archive

Worked intuition

1. Classify crossing intent and direction.

2. Name clock/reset relationship assumptions.

3. Inspect primary metric: reset-domain hazard coverage, unresolved RDC severity count, closure quality.

4. Collect structural plus dynamic evidence.

5. Differentiate real hazard from tool noise.

6. Pick smallest safe fix and define regression matrix.

7. Document signoff rationale or waiver ownership.

Common misconceptions

• CDC clean report means protocol is proven.

• All resets are equivalent if assertion works.

• Gray code alone guarantees FIFO correctness.

• Waivers are harmless schedule shortcuts.

Visual reinforcement

RDC methodology loop

intent capture -> structural run -> dynamic proof
        -> waiver board -> milestone gate -> archive

Layer responsibilities

CDC/RDC OWNERSHIP LAYERS — RDC Methodology

layer                 owns                            common failure
------------------    -----------------------------   -----------------------------
design intent         crossing architecture           wrong topology selected
protocol semantics    req/ack, fifo, ordering        liveness/deadlock bugs
reset behavior        assert/deassert sequencing      boot instability
analysis setup        tool rules + waivers            false confidence
signoff governance    risk acceptance + dashboard     stale critical waivers

CDC/RDC deep dive

RDC closure must connect IP assumptions to SoC reality.

Concept diagram

RDC CLOSURE

IP reset intent + SoC sequencing -> structural checks -> dynamic stress -> signoff

Metric graph

MILESTONE READINESS

M-2 55%
M-1 82%
M0  100%

Reports and artifacts

• top-level RDC opens

• reset simulation coverage

• chip integration blockers

• waiver backlog

Mini case study

Each IP was locally clean, but top-level sequencing violation created cross-subsystem boot intermittency.

Debug branches

• Audit subsystem assumptions

• stress chip-level reset scenarios

• close ownership gaps

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.

Theory reinforcement

RDC signoff makes reset behavior measurable, reviewable, and reproducible.