element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • 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 & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
PicoZed Hardware Design GTX transceivers
  • 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 Verified Answer
  • Replies 15 replies
  • Subscribers 338 subscribers
  • Views 2562 views
  • Users 0 members are here
Related

GTX transceivers

Former Member
Former Member over 10 years ago

Hi..

I am working with GTX transceivers on the 7030.  I am trying to configure the GTXE2_CHANNEL_X0Y1 transceiver attached to SMA on the Carrier board using Aurora 8b10b example design.
I instantiated the aurora_example design to the processing wrapper.  This only have the zynq processing with 2 pl_clocks required in Aurora.

In the file.xdc I am doing this configuration.  I donu00B4t know if it is right,
#######################################################
set_property PACKAGE_PIN U9 [get_ports GTXQ0_P]
set_false_path -through [get_pins -hier *cdc_to*]
set_property LOC GTXE2_CHANNEL_X0Y1 [get_cells aurora_module_i/aurora_8b10b_0_i/U0/gt_wrapper_i/aurora_8b10b_0_multi_gt_i/gt0_aurora_8b10b_0_i/gtxe2_i]
set_property DONT_TOUCH true [get_cells ProcessingSystem_i]
set_property DONT_TOUCH true [get_cells ProcessingSystem_i/processing_system7_0]
set_property DONT_TOUCH true [get_cells ProcessingSystem_i/processing_system7_0/inst]
set_property DONT_TOUCH true [get_cells ProcessingSystem_i/util_ds_buf_0]
set_property PACKAGE_PIN Y8 [get_ports RXN]
set_property PACKAGE_PIN W8 [get_ports RXP]
set_property PACKAGE_PIN Y4 [get_ports TXN]
set_property PACKAGE_PIN W4 [get_ports TXP]

#######################################################

I got this  error in the implementation, and I have no idea what is the reason:

[Place 30-378] Input pin of input buffer Communication_block/aurora_module_i/U0/clock_module_i/init_clk_ibufg_i has an illegal connection to a logic constant value.
[Place 30-99] Placer failed with error: 'Implementation Feasibility check failed, Please see the previously displayed individual error or warning messages for more details.'
Please review all ERROR, CRITICAL WARNING, and WARNING messages during placement to understand the cause for failure.

Please help


  • Sign in to reply
  • Cancel
Parents
  • drozwood90
    0 drozwood90 over 10 years ago

    I received a response from one of our specialists.  He mentioned that my thinking the RXUSRCLK needing to be higher was incorrect.  Here is an excerpt from his e-mail:

    "In fact 97MHz is exactly the right frequency for those clocks. The RXUSRCLK is determined by the (serial line rate) / (Internal data width). Its mentioned on the thread that they are operating at a line rate of 3.125Gbps, and most likely they have the data width set to 32 (IBERT default setting.)

    So given all this I would expect the RXUSRCLK = 3.125G / 32 = 97.656250 MHz

    If RXUSRCLK2 is also equal to 32 then RXUSRCLK2 = RXUSRCLK.

    All of this is explained in detail in the GTX user guide.

    "

    So, I think that now that you have your regional settings changed, also armed with the above knowledge,  I think you are all set!

    Please let me know if you agree!

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Reply
  • drozwood90
    0 drozwood90 over 10 years ago

    I received a response from one of our specialists.  He mentioned that my thinking the RXUSRCLK needing to be higher was incorrect.  Here is an excerpt from his e-mail:

    "In fact 97MHz is exactly the right frequency for those clocks. The RXUSRCLK is determined by the (serial line rate) / (Internal data width). Its mentioned on the thread that they are operating at a line rate of 3.125Gbps, and most likely they have the data width set to 32 (IBERT default setting.)

    So given all this I would expect the RXUSRCLK = 3.125G / 32 = 97.656250 MHz

    If RXUSRCLK2 is also equal to 32 then RXUSRCLK2 = RXUSRCLK.

    All of this is explained in detail in the GTX user guide.

    "

    So, I think that now that you have your regional settings changed, also armed with the above knowledge,  I think you are all set!

    Please let me know if you agree!

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Children
  • Former Member
    0 Former Member over 10 years ago in reply to drozwood90

    Thank you Dan

    It has been very valuable help..

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify 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