We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Showing results for 
Search instead for 
Did you mean: 
Visitor mikekam
Registered: ‎09-25-2012

Metastability duration estimation for the Spartan 6

While reviewing an existing design, a violation of the standard rule using 2 FF's to sync an asynchronous signal was discovered. In this case, the logic is looking for an edge detect, but only uses a single FF to capture the first edge of the signal.

Is there a way to estimate what the settling time of the metastable condition would be from the first FF, through the AND gate, to the input of second FF? The clock rate is slow (<10MHz), so there is more than 100ns allowed for settling.


0 Kudos
2 Replies
Registered: ‎08-14-2007

Re: Metastability duration estimation for the Spartan 6

You'd need the exact timing numbers to know what the routing delays are, but it would be

unusual for the total to exceed a handful of nanoseconds.  If you can find the path in a

timing report, the slack would be the number that says how much settling time you have.

If not, you could find the routes in the FPGA editor and get the delay, then add the datasheet

values for clock to out of the driving flop, combinatorial delays through the logic for the AND

gate (this could be a LUT or other logic, you'd need to inspect the slice in the FPGA editor)

and then subtract the total from the clock period.  Even if you waved your hands, and said

it couldn't be more than 20 ns and you have 80 ns to settle, I would expect that any

metastable event that takes that long to settle would be a once in the age of the universe

sort of event.

-- Gabor
0 Kudos
Visitor mianni
Registered: ‎09-21-2015

Re: Metastability duration estimation for the Spartan 6

Hello! I am doing a Survey paper about metastability in the Spartan-6 board. If i understand it correct there are a lot of timing issues to considerate that can create an asynchronous signal in a D flip-flop. This can lead to a metastable state in worst case scenario. For that topic i have some information.


The problem arise is when i try to find what kind of D flip-flop is used in Spartan 6 and on what kind of bulk it is placed in , i.e. 65nm CMOS bulk. I need this for creating some evaluation of the characteristics of the flop.


Regards Marco.

0 Kudos