Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
when you a multi clock domain ckt, and when two clocks reach the same logic endpoint from different paths ...you have a reconvergence problem..you need to either delay one clock or use some clock domain syncronization techniques to avoid this...
when you a multi clock domain ckt, and when two clocks reach the same logic endpoint from different paths ...you have a reconvergence problem..you need to either delay one clock or use some clock domain syncronization techniques to avoid this...
My thinking it is a single clock domain. If two clocks seem to converge than it is more or less a overlapping clocks problem and does not fall into clock convergence.
In static-timing-analysis, clock-reconvergence describes the situation where you perform multi-corner (best-case, worst-case) analysis. For a timing-path in your design, there are two important flops: driving-flop and capture-flop. If these two share part of the clock-tree, then 'reconvergence' refers to the timing-analyzer's treatment of the clock-tree delay.
pessimistic reconvergence means the analyzer will always pick the 'worst-case' timing independently for drivingflop and capture-flop.
optimisitc reconvergence means the analyzer will use the same offset for the part of the clock-tree common to both flops. This is more realistic, since in the physical sense, one part of the clock-tree cannot run at worst-case and best-case corner simultaneously.
In clock-tree synthesis (CTS), reconvergence is when any node in your clock-tree has more than one input (fan-in) from itself. For example, a lot of designs have bypassable-PLL circuits. If the bypass-mux is in the RTL, then the CTS-tool thinks the primary-port branches out to two distinct branches, which then 'collapse' back into itself. (If the bypass-mux is in the PLL macro, then the tree still reconverges, but it is hidden from the CTS-tool.)
Reconvergence is not necessarily a bad thing -- it just makes ASIC-engineer's life more complicated.
i like modelsim62c's answer
there are two interpretations. i wish there was more detail in the first one though, because the second one seems to be more popular.
You can find few important information in the following path also. In one of the thread I was mention but I forget that .. so pasting the link once again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
