A crossing list is only as complete as the clock list behind it. This topic turns "what clocks do we have?" from hallway knowledge into a written inventory: sources, generated clocks, gated and muxed clocks, the resets that go with them, and the intent document that signoff checks against.
Lesson | After it you can... |
|---|---|
List every clock and reset source and say which domain each flop belongs to. | |
Decide when a divided, gated or muxed clock is a new domain. | |
Explain why "static" must be enforced, not assumed. | |
Write the tool-neutral clock-intent table a CDC setup needs. |
Read them in order: inventory first, then the tricky generated clocks, then the signals that pretend to need no clock, then the document that records it all.
Because a synchroniser answers a known crossing, and the crossing list comes from the clock list. An unknown clock means unknown crossings, which no synchroniser choice can fix.