Clock domain crossing
From Wikipedia, the free encyclopedia
A clock domain crossing (CDC), or simply clock crossing, is when a signal crosses from one clock domain into another. If a signal does not assert long enough and is not registered, it may appear asynchronous on the incoming clock boundary.[1]
Synchronizing a signal that crosses into a higher clocked domain can be accomplished by registering the signal through a flip-flop that is clocked by the source domain, thus holding the signal long enough to be detected by the higher clocked destination domain. Synchronizing a signal traversing into a slower clock domain is more cumbersome. This typically requires a register in each clock domain with a form of feedback from the destination domain to the source domain, indicating that the signal was detected.[2]
Contents |
[edit] Clock Domain Crossing Tools
These are some tools that support clock domain crossing.
- Meridian CDC by Real Intent
- Encounter Conformal Equivalence Checker with Clock Domain Checks
- SpyGlass-CDC by Atrenta
- 0-In Clock-Domain Crossing (CDC) by Mentor Graphics
- Leda by Synopsys
- Indigo by Blue Pearl Software
[edit] See also
[edit] References
- ^ Parker, Roy H., Caution: Clock Crossing A prescription for uncontaminated data across clock domains, Chip Design Magazine, Issue 5, Article 32, July 2004.
- ^ Stein, Mike, Crossing the abyss: asynchronous signals in a synchronous world, Paradigm Works, EDN Magazine, 24 July 2003.
[edit] External links
- Understanding Clock Domain Crossing Issues
- White Paper on Clock Domain Crossing
- Clock Domain Crossing Article - Simulation Falls Short with Asynchronous Clocks
- Technical Paper on Clock Domain Crossing - A Comparison of Metastability Modeling Methods
 |
This electronics-related article is a stub. You can help Wikipedia by expanding it. |
