Continue to Site

Welcome to EDAboard.com

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.

Register Log in

Why does clock latency need to decrease?

Status
Not open for further replies.
I

identical

Member level 1
Joined
Feb 10, 2015
Messages
33
Helped
0
Reputation
0
Reaction score
0
Trophy points
6
Activity points
225
If clock latency is the difference in clock arrival at a particular flop compared to the clock source then why do we even care about latency.

for eg : if skew is 0 at latency 500 ps (500ps for both launch flop and capture flop) then why would it even factor in setup or hold violations since it is the same for both flops. The skew may vary.
 

it is not that simple, latency is not a 'single number', it is a 'range' because of variation.

say flopA has a latency of 5, meaning there are 5 inverters on the clock tree path that leads to flopA. Now say flopB has a latency of 5 as well, but the inverters are different. In theory, you would think the clock signal would arrive at the same time at both flops. In reality, all of these inverters will behave slightly different because of variation. You need best case and worst case scenarios for launch and capture.

that is why your goal should be to minimise latency and skew. they are both correlated and cannot be assessed individually.
 
Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top