in Hold analysis weather the phi (clk -q +combination delay ) also include setup time .
@snehilrathod23228 жыл бұрын
If the edge is same to evaluate the hold time, and as you said gitter doesn't matter for hold since its the same edge. Then why do we still have to consider the uncertainty (HU)
@palanisamy76657 жыл бұрын
how to rectify hold time violation.. as you said for setup time by increasing clock time??
@VLSISystemDesign7 жыл бұрын
Hi Palani You can add buffers in datapath or all clock buffers in launch clock path. Also, increasing clock time for setup time is the last option to resort to. Ideally, you should be trying to fix setup time without increasing clock period
@palanisamy76657 жыл бұрын
thanks for your valuable reply!!!!
@singaluriram8 жыл бұрын
Thank you sir
@VLSISystemDesign8 жыл бұрын
You are most welcome Vijay
@ashishsrivastava626910 жыл бұрын
if setup time is mux 1 delay and hold value is mux2 delay then sum of mux1+mux2 is clock-q delay ??? if yes i have timing report file in which i have i have setup value 0.352 but clk-q delay 0.120.
@tausid9795 жыл бұрын
why pulse at zero nanosec reaching at both flop in case of hold time analysis
@CopyPasteGrow4 жыл бұрын
in setup time we analyse the problem at two different time instants. We analyse like "let's at t=0 if launch flop is sending some data then what will happen at t=T at recieving flop". I am taking ideal scenario here. and for Hold analysis we analyse both ends at the same time i.e. at recieving flop we are analysing previous input which was given at t=-T. So we are analysing "what is happening at both the flops at the same instant of time."