Please Like, Share and Subscribe to my channel kzbin.info/door/3mTACG8vPWsHQFMfxzeDZg
@saikumardussa16432 жыл бұрын
Nice explanation sir it wil help for lots of people Keep going 🥳
@Electronicspedia2 жыл бұрын
Thank you 🙂
@MidhunSasikumarpanangat11 күн бұрын
may i suggest that you should add reset isolation techniques to the list of RTL methods. its a commonly used method
@lakshmi-kb4ww Жыл бұрын
Thank you good explanation
@akshaykumarmane15277 ай бұрын
its very useful. please provide something on power domain crossing
@Rajat0607 Жыл бұрын
Thank you for your videos. They are amazing Can you pls tell us more about your professional background ?
@Electronicspedia Жыл бұрын
Please take a look into Electronicspedia about page.
@manpreetkaurjaswal1175Ай бұрын
why is the double synchronizer out in Reset domain 2; shouldn't we send synchronised output from domain1 itself?
@user-qs9wg3dn3g8 ай бұрын
Thanks sir, its very helpful. please provide us with docs/pdfs , if available, so that we can revise the things.
@manpreetkaurjaswal1175Ай бұрын
what would happen in case of synchroniser fix if rstn2 signal changes while we are recieveing data in synchroniser from reset domain 1
@azrsn5596 Жыл бұрын
Nice video though i do have a few of comments: 1. Fix #1 "RTL fix" is risky advice as it will not work for a multibit signal. If you a multibit signal RDC we must treat it as asynchrous from the destination side and synchronize it with one if the known CDC methods (e.g asynchronous FIFO...). 2. Isn't fix #3 also technically an RTL fix? 3. fix #4 is not a fix. rather constraints are a necessary step of reset ordering. waivers of course don't fix anything either.
@Electronicspedia Жыл бұрын
Hi, your comments are all valid and i completely agree. Fix 4 is not really a fix, it's more of a waiver through review. And it should be used only when design is right by architecture and reset ordering is done in the right order. .
@RandomHubbb4 ай бұрын
2nd case is very confusing, i think it is a bad example to begin with. why would someone assert reset in domain 1 but then deassert reset in domain 2. what kind of functional use case is that to begin with?
@chessten2 жыл бұрын
Hi, for the RTL fix technique, instead of double synchronizer, can it be just 1 flop? Since the destination flop can act as the 2nd stage synchronizer itself?
@Electronicspedia2 жыл бұрын
Hi, Regular Flops should not be used as synchronizers, because in placement and route these regular Flops might get placed at far distances, which decreases MTBF, hence leads to failure. Instead we always use synchronizers which are standard cell components that's why we have synchronizer and then flop in destination.
@chessten2 жыл бұрын
@@Electronicspedia ahh, thanks.
@ashishpudi4 Жыл бұрын
@@Electronicspedia we need to give same clock what we given in flop1 to Double flop synchronizer ? and rstn2 is deasserted during that time as well ?
@Electronicspedia Жыл бұрын
Yes same clock for both flops.
@user-he1gf2ix4b6 ай бұрын
Sir what to do if we have to apply clock domain crossing and reset domain crossing together?
@Sachindeo932 жыл бұрын
Is double synchronizer similar to two F/F synchronizer used for CDC?
@Electronicspedia2 жыл бұрын
Yes, double synchronizers and Two stage synchronizers are the same.
@Sachindeo932 жыл бұрын
@@Electronicspedia Btw thank you for such an excellent explanation. You have explained such a difficult to grasp concept in such a simplified manner!
If we have different clock domains as well with different reset domains. How to fix it
@Electronicspedia2 жыл бұрын
If we have different clock domains and reset domain then we may to include synchronizers and also we need to solve the issue with reset ordering.
@RanjanSingh-pm6ze2 жыл бұрын
sir how we will know that reset one is asserted and now gated clock should be turn on. AS you have explained that when reset1 will de-asserted gated clock of second flop will be off, and when reset1 will be asserted then gated clock will be on. so how we will know that weather it is asserted or not?
@Electronicspedia2 жыл бұрын
Hi Usually system resets will be software controlled, so you know when the reset is going to assert or deassert. If some resets do not have software override and if they are completely hardware based then you might get info from FSM state and/or you can add simple edge detection logic to check whether reset is asserted or not.