Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Path
  • CDC/RDC Glossary
  • CDC/RDC Metrics Reference
  • CDC/RDC Interview Prep
  • CDC/RDC Signoff Cheatsheet
  • Clock Domains and Failure Modes8
  • Metastability and Synchronizers16
  • CDC Protocols and Handshakes16
  • Reconvergence and Gray Coding16
  • Reset Domain Crossing16
    • Reset Deassertion CDC
    • Reset Sequencing
    • RDC Structural Checks
      • What Is an RDC Crossing
      • RDC Categories
      • Reset Ordering Violations
      • Reading RDC Findings
    • Reset Debug Playbook
  • Architecture and Design Rules16
  • CDC Signoff Methodology24
  • RDC Signoff16
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹RDC Structural Checks
  1. Topics
  2. CDC & RDC
  3. Reset Domain Crossing
  4. RDC Structural Checks
  5. Reading RDC Findings

Part 5 · Reset Domain Crossing · All levels

Reading RDC Findings

Triage on a clearly illustrative generic excerpt: sort, fix, waive with evidence, and re-check.

A findings list is triaged, not merely read. The goal of a first pass is to sort every entry into fix, waive with evidence, or needs-design-decision, and to clear the unambiguous structure bugs before spending review time on the architectural ones.

The excerpt below is fabricated and labelled illustrative: it shows the shape of triage thinking, not any real report. Work the generic shapes from the previous lesson, never message text.

Diagram
illustrative findings excerpt (fabricated triage example, not tool output)
R1  different-reset, ctrl_a -> ctrl_b ......... no protection ............ FIX: synchronise
R2  different-reset, cfg_static -> ctrl_c ...... static after boot ........ WAIVE: qualify + re-check intent
R3  combinational gate on reset net rst_b ..... glitch risk .............. FIX: remove gate
R4  release straight from async source, dom D . ....................... FIX: add synchroniser
R5  producer P released before consumer C ............................... DECIDE: sequence or prove harmless
R6  reset used as enable in domain E .................................... FIX: synchronise first

Triage order

  1. Fix the structural rows first (R3, R4, R6, R1): each has one standard fix, and each fix can change what the remaining findings mean.

  2. Re-analyse after the fixes: some ordering and different-reset findings disappear or change shape once the reset nets are clean.

  3. Decide the architectural rows (R5) with the designer: sequence the pair, add a ready flag, or run the adversarial release-order test as evidence.

  4. Waive last (R2): a waiver records the claim (static after boot), the evidence (qualification logic plus intent), the reviewer, and the condition that reopens it (any change to the reset structure).

Tip

Count the list honestly: open findings, fixed findings, and waived findings with live evidence are three separate numbers. A shrinking open count means progress; a growing waived count without new evidence means the bar is slipping.

Check yourself Why are structural fixes done before architectural decisions in triage?

Because each structural fix changes the reset nets the remaining findings were reported against: ordering analysis and waivers written before the fixes may describe circuitry that no longer exists.

Check yourself What must a waiver record beyond the reason?

The evidence behind the claim, an independent reviewer, and the condition that reopens it, typically any change to the reset structure. A reason alone is an opinion, not a waiver.

Related topics

  • RDC categories

  • Debug checklist

Previous

74 / 179

Next: Reset Debug Playbook

Up next

Up nextReset Debug Playbook

Sign in to save progress

Practice this lessonReport an error

See also

  • What Is an RDC Crossing
  • RDC Categories