element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultrazed Hardware Design UltraZed-SOM Carrier Card Clock Generator Concern
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 323 subscribers
  • Views 1393 views
  • Users 0 members are here
  • ultrazed
Related

UltraZed-SOM Carrier Card Clock Generator Concern

timesnewramen
timesnewramen over 4 years ago

I am designing a carrier card for the UltraZed SOM, and wanted to use a similar design for a reference clock for high-speed SERDES communication as the Avnet Carrier Card design here: https://www.avnet.com/opasdata/d120001/medias/docus/190/UZ-EV-CC-UG-ver1.pdf

Since page 43 of that guide mentions using the 8T49N241 (datasheet https://www.renesas.com/us/en/document/dst/8t49n241-datasheet) in LVDS configuration for one of its output clocks as the GTH reference clock, I thought I would use this component (or the newer 8T49N242).
However, I noticed that, in the LVDS specifications for the output clock in Table 8H of that datasheet, the minimum differential voltage swing of the clock signal is 200 mV, while, according to Table 97 of XIlinx UltraScale+ AC and DC switching characteristics document DS925 (link: https://www.xilinx.com/support/documentation/data_sheets/ds925-zynq-ultrascale-plus.pdf ), the minimum differential voltage swing of a GTH reference clock is 250 mV.

Is this not a problem? the minimum differential voltage swing of the clock generator is less than the minimum differential voltage swing required by the Xilinx MPSoC by 50 mV. Does this need to be remedied for reliability?

  • Sign in to reply
  • Cancel

Top Replies

  • bhfletcher
    bhfletcher over 4 years ago in reply to bhfletcher +1 suggested
    Doing a bit more research on this (haven't heard back from Renesas yet), it appears that the issue is in semantics with how Xilinx is specifying V IDIFF , which is defined as the ZU+ GTH Transceiver Clock…
  • bhfletcher
    0 bhfletcher over 4 years ago

    I'm looking into this. I've asked Renesas for clarification on their definition as this document shows the 8T49N241 used as a reference clock for the Xilinx Zynq UltraScale+ GTH transceiver reference clock.
    https://www.renesas.com/us/en/application/winning-combinations/xilinx-zynq-ultrascale-mpsoc-power-and-timing

     

    Bryan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bhfletcher
    0 bhfletcher over 4 years ago in reply to bhfletcher

    Doing a bit more research on this (haven't heard back from Renesas yet), it appears that the issue is in semantics with how Xilinx is specifying VIDIFF, which is defined as the ZU+ GTH Transceiver Clock Input Differential peak-to-peak input voltage. I think it is very confusing. I feel better knowing that I am only one of many that Xilinx has confused. At some point, we can all hope that Xilinx will change how they specify this in their datasheet. See the following:

    https://forums.xilinx.com/t5/Serial-Transceivers/Interfacing-to-GTH-Transceiver-Clock/td-p/1136286

    https://forums.xilinx.com/t5/Serial-Transceivers/Virtex-7-GTH-Increase-in-Minimum-Differential-Input-Voltage-for/td-p/88…

    https://forums.xilinx.com/t5/Serial-Transceivers/Interpretation-of-MGT-Reference-Clock-Differential-Input-Voltage/td-p/9…

    https://forums.xilinx.com/t5/Serial-Transceivers/GTH-transceiver-voltages/td-p/1134614

    https://forums.xilinx.com/t5/Serial-Transceivers/Ultrascale-kintex-MGTREFCLK-voltage/td-p/975535

    https://forums.xilinx.com/t5/Serial-Transceivers/MGT-Reference-Clock-Input-Common-Mode-Voltage/td-p/942538

     

    If I interpret what I see in these various forum posts, it would appear that Xilinx defines VIDIFF as

    [MAX(MGTREFCLK_P - MGTREFCLK_N) - MIN(MGTREFCLK_P - MGTREFCLK_N)]

     

    whereas the Renesas definition is

    MAX(MGTREFCLK_P) - MIN(MGTREFCLK_N)

     

    Using some real numbers helps illustrate this. Let's assume an output differential voltage of 200 mV centered around a common mode voltage of 0.9V. That means the signals are swinging between 0.8V and 1.0V.

    • When MGTREFCLK_P = 1.0, then MGTREFCLK_N = 0.8V, so MGTREFCLK_P - MGTREFCLK_N = 200 mV
    • When MGTREFCLK_P = 0.8, then MGTREFCLK_N = 1.0V, so MGTREFCLK_P - MGTREFCLK_N = -200 mV
    • Which then leads to 200mV - (-200mV) = 400mV, which is well within the 250mV minimum spec.

     

    To me, this method of figuring is very confusing, but that appears to be the way Xilinx is doing it. If someone else has a better way of explaining it, please do!

     

    Bryan

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube