Reset Domain Crossing

Section goal

Asynchronous reset release, reset sequencing policies, RDC structural analysis, and reset-focused debug playbooks.

How to study this section

1. Start with topic hubs to classify problem shapes.

2. Use mechanism and reports pages to connect risk signals to evidence.

3. Practice debug and worked examples before signoff reviews.

4. Close with checklist and silicon impact before approving fixes or waivers.

Topics

1. reset-deassertion-cdc/ — Reset Deassertion CDC

2. reset-sequencing/ — Reset Sequencing

3. rdc-structural-checks/ — RDC Structural Checks

4. reset-debug-playbook/ — Reset Debug Playbook

Related topics

• CDC/RDC course hub

CDC/RDC deep dive

Reset release ordering is a first-order reliability contract.

Concept diagram

RESET RELEASE FLOW

assert global -> clocks stable -> sync release per domain -> first transaction

Metric graph

BOOT STABILITY

passes per 1k boots: 920 -> 980 -> 999

Reports and artifacts

• reset dependency matrix

• RDC warning classes

• boot stress logs

• waiver aging

Mini case study

Domain B released before producer A was valid, causing rare startup deadlock.

Debug branches

• Correlate reset and clock timelines

• verify async assert/sync release

• exercise skewed release tests

Senior review question

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