Thank you, sir. I have the following query: If the jitter source is from the common CLK, why do we need to consider it in Setup uncertainly? Shouldn't the jittered clocks (FF1/CK, FF2/CK) edges be moving in the same direction?
It is a great video!!! I think the accuracy check (such as Min pulse width check, Min period check, clock as data check, ... ) is an interesting topic. Could you consider my suggestion?
Hi Kankanala, We consider the skew in uncertainty only in preCTS stage. Once the clock tree is build, we have actually skew so we dont consider the skew in uncertainty. Watch again at @11:27, it will be clear.
why are we considering setup/hold margin in uncertainty while we are also considering it for setup/hold calculation? (The margin in uncertainly refers to something else I think)
Hi Akash, Positive slack is called the margin. In a particular data path if you want to fix setup, means you are going to reduce the delay of that data path, It may violate your hold. so you must have hold margin on that path and vice-versa.
Keep uploading sir👍🙏
Sure 👍, keep supporting...
Sir in pre-cts u mentioned latency is negligible then how u calculate the skew(capture latency - launch latency)
Thanks, a really good video. And it will be better If here are subtitles
Thanks Yuxiang,
It is my pleasure that you loved the video. I will try to add subtitle.
Nice video and explanation
Thanks a lot Niteesh. Stay tune and keep learning.
Thank you, sir. I have the following query: If the jitter source is from the common CLK, why do we need to consider it in Setup uncertainly? Shouldn't the jittered clocks (FF1/CK, FF2/CK) edges be moving in the same direction?
Hi Sudipto,
Yes, right. But in setup analysis launch and capture clock edges are different, and jitter is associate with edge.
@@TeamVLSI Yes sir, I missed that part. Thanks for the explanation.
Can you please do video on clock gating and asynchronous checks in vlsi
Thanks for explanation
Always welcome Komal,
Keep watching, Keep supporting...
hi sir, at time stamp 13.58 we are using uncernity (skew +margin+jitter) then why another skew componet ...is this calculation in post cts
Uncertainty will relax after CTS has built and we will keep uncertainty for synthesis to meet setup timing
It is a great video!!! I think the accuracy check (such as Min pulse width check, Min period check, clock as data check, ... ) is an interesting topic. Could you consider my suggestion?
Thanks for the tips!
We add skew in setup uncertainty only right( given formula), then why we added seperately at 13:15
Hi Kankanala,
We consider the skew in uncertainty only in preCTS stage. Once the clock tree is build, we have actually skew so we dont consider the skew in uncertainty.
Watch again at @11:27, it will be clear.
why are we considering setup/hold margin in uncertainty while we are also considering it for setup/hold calculation? (The margin in uncertainly refers to something else I think)
I would love to see other name, If you have details Please share.
THNK U
Welcome 😊
how to define the uncertainty value in sdc?
Hi VP,
Watch the full video, although at time 12:30 , it is explained.
Why uncertainty is High in Half cycle paths?
Hello sir,
Who will set this uncertainty value?
Synthesis ppl?
Yes
sir what is setup and hold margins? why are they required?
Hi Akash,
Positive slack is called the margin.
In a particular data path if you want to fix setup, means you are going to reduce the delay of that data path, It may violate your hold. so you must have hold margin on that path and vice-versa.
@@TeamVLSI Yes thank you !
Nice sir
Thanks Arun. keep supporting...
in RAT calculation you have taken time period in setup analysis but you have not taken time period in the hold analysis . why ???
Hi Vikas,
The answer is simple, We check hold on the same edge not on the next edge like setup.