Breaking News
Comments
Newest First | Oldest First | Threaded View
Richard_Brabant
User Rank
Rookie
re: Does anyone here know the theoretical justification for a synchronizer with more than two stages?
Richard_Brabant   4/24/2012 2:09:39 PM
NO RATINGS
Hello, I assume the "MTBF formula" is known. Then the list of physical events to check and drive is long: 1- Tau, you talked already about it. 2- Danger window during a clock cycle, this is depending of the quality of the synchronizer. That is an other reason a specific synchronizer flop is designed with specific characteristics. 3- Frequency to synchronize to. Not a lot to do about it, this speed is driven by the project needs. 4- Frequency of the changes of the input to synchronize. Not a lot to do about it, it is what the functionality needs. ***** Now from this point what is relatively ignored: 5- The input is supposedly fully asynchronous or random in regards to the synchronizer clock. In other words the input is along the time evenly distributed all along the clock period of the synchronizing clock. However in many applications the different clocks are related to each others. Here the consequences are very important and I don't have place for developing the consequences, but they are very important. 6- The input signal is supposedly to be transitioning instantaneously, what is not the case and that is someway changing the point "2" the danger of window. The very important point to check in the design that is a good powerful driver as last stage of the signal to synchronize. No long interconnection and slow ramp transition. If you are interested by the topic join us at: http://www.linkedin.com/groups/CDC-clock-domain-crossing-in-3748476?gid=3748476&trk=hb_side_g LinkedIn group: CDC - clock domain crossing in ASIC/SOC Best regards. Richard.

old account Frank Eory
User Rank
Rookie
re: Does anyone here know the theoretical justification for a synchronizer with more than two stages?
old account Frank Eory   4/16/2012 10:59:04 PM
NO RATINGS
It's purely a statistical MTBF thing. Each additional flip flop stage increases the MTBF exponentially. The classic equations for metastability show an inverse relationship between MTBF and clock frequency. This intuitively makes sense -- the faster the clock, the more likely the flip flop will fail to resolve a metastable condition in the required time, i.e., before the next clock edge. As you add additional flip flop stages, the probabilities of synchronizer failure multiply and the MTBF goes up exponentially. It does seem odd that we have to be comfortable with circuits that "probably" won't fail, but its easier to get comfortable when the probabilities become absurd. The often-used 2 flip flop resynchronizer can result in MTBFs of thousands of years for many systems. If that's not good enough, add another stage or two and pretty soon you're looking at MTBFs exceeding the age of the universe.

ese002
User Rank
Rookie
Does anyone here know the theoretical justification for a synchronizer with more than two stages?
ese002   4/16/2012 4:06:31 AM
NO RATINGS
The classic two flop synchronizer works on the principle that, even if the first flop becomes metastable, there will be enough time for it to recover and meet the setup requirement for the second flop. Here and there (most recently at a talk given at Mentor's U2U conference) I have heard mention of synchronizers with three and even four stages. According to the speaker, these extra stages are necessary when the metastability recover time (he called it “tau”) is excessive relative to the clock period. This problem occurs when low voltages flops need to operate at high clock frequencies. Unfortunately, I did not get the opportunity to ask how the extra stages were supposed to help. It seems to me that if there is not enough time for the first flop to stabilize before feeding flop #2 then there won't be enough time between flop #2 and #3 either. And the same for between #3 and #4 or between any two flops in the chain no matter how long you make it. Is it simply statistical? The Xilinx speaker at U2U did say that “tau” was not strictly deterministic. Perhaps the chance that all three leading flops will experience long metastability recovery times is remote enough that the problem can be considered solved. I'm not sure I'm comfortable with having circuits that “probably” won't fail feeding circuits that assume their input their inputs never fail. It occurs to me that a safer solution might be to divide the clock by two and drive the clock inputs of a conventional two stage sychronizer with this half-rate but still synchronous clock. The first flop now has twice the time to recover at the cost of additional latency. It even occurred that Xilinx could be using this method but the speaker was quite explicit about four flops. Any insights?



EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

What's the Best Traveling Toolkit?
Max Maxfield
13 comments
A few years ago at a family Christmas party, I won a pocket knife as part of a "Dirty Santa" game. This little scamp was a Buck 730 X-Tract. In addition to an incredibly strong and sharp ...

Rishabh N. Mahajani, High School Senior and Future Engineer

Future Engineers: Don’t 'Trip Up' on Your College Road Trip
Rishabh N. Mahajani, High School Senior and Future Engineer
10 comments
A future engineer shares his impressions of a recent tour of top schools and offers advice on making the most of the time-honored tradition of the college road trip.

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
41 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...

Karen Field

July Cartoon Caption Contest: Let's Talk Some Trash
Karen Field
159 comments
Steve Jobs allegedly got his start by dumpster diving with the Computer Club at Homestead High in the early 1970s.

Top Comments of the Week
Flash Poll
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)