Breaking News
Comments
Newest First | Oldest First | Threaded View
JoelB01
User Rank
Author
re: Understanding clock domain crossing issues
JoelB01   6/21/2013 7:00:03 PM
NO RATINGS
There is another issue with data coherency that you did not address. The trace delay for all bits in the "A" bus must be approximately the same, and should be less than the period of C2. Unfortunately, it is common to "false_path" the data from FA to FB, which allows the tools to violate this requirement. This is especially a problem in the case where C1 and C2 are asynchronous clocks that are nearly the same frequency, and that frequency is fairly high. For example, with a frequency of 400MHz, the C2 period is just 2.5ns. If A is a 6-bit Gray coded value, and the the data delay for most bits of A ~0.5ns, while the delay for A[1] is much larger (5.5ns, 2 full C2 clock cycles later), you can run into an issue where the receiver gets a Gray code sequence that can lead to problems: Sent: 001100 001101 001111 (bit 1 transitions) 001110 (bit 0 transitions) 001010 (bit 2 transitions) Received: 001100 001101 001100 (bit 0 transition!) 001010 (bit 1 and 2 transition) In this event, the Gray code that the receiver sees appears to have decremented (from 001101 to 001100), where it should have only incremented. We have been able to address this problem in the Xilinx FPGA tool flow using a TIMESPEC with DATAPATHONLY, but have not been able to find a solution for this issue in the Altera FPGA tool flow.

old account Frank Eory
User Rank
Author
re: Understanding clock domain crossing issues
old account Frank Eory   5/31/2013 8:26:06 PM
NO RATINGS
Thanks for this excellent article and very thorough coverage of CDC problems and their solutions.

I_B_GREEN
User Rank
Author
re: Understanding clock domain crossing issues
I_B_GREEN   9/28/2012 5:29:50 PM
NO RATINGS
Your pictures gloss over hold up times



Datasheets.com Parts Search

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

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.
Like Us on Facebook
Special Video Section
The quality and reliability of Mill-Max's two-piece ...
01:34
The quality and reliability of Mill-Max's two-piece ...
LED lighting is an important feature in today’s and future ...
05:27
The LT8602 has two high voltage buck regulators with an ...
05:18
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
01:34
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...
The LT®6375 is a unity-gain difference amplifier which ...
The LTC®4015 is a complete synchronous buck controller/ ...
10:35
The LTC®2983 measures a wide variety of temperature sensors ...
The LTC®3886 is a dual PolyPhase DC/DC synchronous ...
The LTC®2348-18 is an 18-bit, low noise 8-channel ...