Transcription of CloCks Understanding clock domain crossing issues
{{id}} {{{paragraph}}}
EE Times-India | December 2007 | Saurabh VermaEngineering ManagerAtrentaAshima S. DabareConsulting Applications EngineerAtrentaIntroductionSoCs are becoming more com-plex these days. A lot of func-tionality is being added to chips and data is frequently transferred from one clock domain to anoth-er. Hence, clock domain crossing verification has become one of the major verification challenges in deep submicron designs. A clock domain crossing occurs whenever data is trans-ferred from a flop driven by one clock to a flop driven by another clock . In Figure 1, signal A is launched by the C1 clock do-main and needs to be captured properly by the C2 clock domain . Depending on the relationship between the two CloCks , there could be different types of prob-lems in transferring data from the source clock to the destina-tion clock .
eetindia.com | December 2007 | EE Times-India domain may not capture it in the very first cycle of the destination clock because of metastability.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
Pragmatic Simulation-Based Verification of Clock, Pragmatic Simulation-Based Verification of Clock Domain Crossing, And Jitter using SystemVerilog Assertions, No Man's Land, Clock domain, Clock Domain Crossing, Clock, AND9075 - Understanding Data Eye Diagram, Crossing, Clock jitter, Domain, Texas Instruments, LVDS Application and Data Handbook, SystemVerilog