RDC signoff starts from structure, not simulation: which reset drives each flop, which signals cross between reset domains, and whether each crossing has a synchroniser, isolation, or a documented reason to need neither. A structural analysis lists every such place so each can be reviewed, waived with evidence, or fixed.
Lesson | After it you can... |
|---|---|
Define a reset-domain crossing and say why source-reset assertion corrupts capture. | |
Read each generic finding category and name its typical fix. | |
Interpret release-order findings and say how to clear them. | |
Triage a findings list in a sensible order with waivers that hold up. |
Suggested order: the four lessons in listed order. No lesson quotes any specific tool's messages: categories are generic and every excerpt is labelled illustrative.
Which reset drives the source flop, which reset drives the capture flop, and what protection (synchroniser, isolation, coordinated reset) sits between them.