UPGRADE YOUR BROWSER

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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Participant jplynch
Participant
825 Views
Registered: ‎03-23-2018

XAPP1249 - Editing GTX Common and Low-level Wrapper Files

Jump to solution

XAPP1249 (v1.1) August 14, 2015, page 31-32 has a section describing manual edits that need to be made to the GTX common wrapper file (*_common.v) and lowest level wrapper file (*_gt.v) after generating the IP using version 3.5 of the Transceiver Wizard.

 

I am now using version 3.6 of the Transceiver Wizard and it appears that these edits are still required.  I can easily change the QPLL_FBDIV_TOP value to "80" in <*_common.v> file, but the <*_gt.v> file is opening in "Read-Only" mode.

 

Are the changes to the <*.gt.v> file still required for running SD-SDI mode?    (BTW: I cannot find a "rxosovrden" port anywhere.)

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
1,022 Views
Registered: ‎07-30-2007

Re: XAPP1249 - Editing GTX Common and Low-level Wrapper Files

Jump to solution

This is an advanced application and will require quite a bit more effort than a normal IP that would not require any hand editing.  You should follow the recommendations.  The RXOSOVRDEN port is on the GTXE2_CHANNEL primitive. For 7-series to be able to edit the files you could rebuild a new application without the *.XCI file.  You will have to manually add all of the gt wizard files (or directories) so they can be edited.  You will lose the ability to get automatic updates to the wizard files with new releases of Vivado so you must keep an eye on what updates are made.  The product is mature now and I would not expect a lot of updates. 

 

The official method of making the modifications can be found here: https://www.xilinx.com/support/answers/57546.html

 

 

I know some have successfully just edited the file in question with an editor outside of Vivado but this is not reliable and isn't recommended. 




----------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution
----------------------------------------------------------------------------


View solution in original post

2 Replies
Highlighted
Moderator
Moderator
1,023 Views
Registered: ‎07-30-2007

Re: XAPP1249 - Editing GTX Common and Low-level Wrapper Files

Jump to solution

This is an advanced application and will require quite a bit more effort than a normal IP that would not require any hand editing.  You should follow the recommendations.  The RXOSOVRDEN port is on the GTXE2_CHANNEL primitive. For 7-series to be able to edit the files you could rebuild a new application without the *.XCI file.  You will have to manually add all of the gt wizard files (or directories) so they can be edited.  You will lose the ability to get automatic updates to the wizard files with new releases of Vivado so you must keep an eye on what updates are made.  The product is mature now and I would not expect a lot of updates. 

 

The official method of making the modifications can be found here: https://www.xilinx.com/support/answers/57546.html

 

 

I know some have successfully just edited the file in question with an editor outside of Vivado but this is not reliable and isn't recommended. 




----------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution
----------------------------------------------------------------------------


View solution in original post

Participant jplynch
Participant
748 Views
Registered: ‎03-23-2018

Re: XAPP1249 - Editing GTX Common and Low-level Wrapper Files

Jump to solution

Thank you for the reply and design direction.  Found the RXOSOVRDEN port right where you said it was and will add that port to the higher level wrapper.  It appears that the port is driven by the "rx_cdrhold" signal from a higher level  controller, perhaps Microblaze.

 

 

0 Kudos