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: 
Highlighted
714 Views
Registered: ‎12-18-2018

GT-Debugger Eye-Qualification

Jump to solution

Hello everyone,

 

I have been trying to perform the eye-qualification of a transmission link using GT-Debugger and IBERT+ following the guide found here: AR# 70915.

But I have encountered some problems.

Every time I run the commands from the TCL Console from the Vivado GUI, it tells me that rxout_div is not known in the dictionary, even though it has been sourced from the file insert_gt_dbg_hwproc.tcl

error_GT-debugger.PNGGiving this error

I am working with a VCU118ES-1, with 8 12.5Gbs, bidirectional link.

Is anyone having the same problem, or found any possible solution?

Thank you in advance for your help

 

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
672 Views
Registered: ‎10-19-2011

Re: GT-Debugger Eye-Qualification

Jump to solution

Hi @alessandro.ottino,

your init step did not finish correctly. For GTY you would need to tell the tool if your line rate is higher or lower than 10Gbps as there are different settings necessary in both cases.

As you run with 12.5Gbps your init command should look like this:

igd_eyescan init cX0Y28 gty_linerate_smaller10=0

With this the run should be possible.

------------------------------------------------------------------------------
Don't forget to reply, give kudo and accept as solution
------------------------------------------------------------------------------
4 Replies
Xilinx Employee
Xilinx Employee
673 Views
Registered: ‎10-19-2011

Re: GT-Debugger Eye-Qualification

Jump to solution

Hi @alessandro.ottino,

your init step did not finish correctly. For GTY you would need to tell the tool if your line rate is higher or lower than 10Gbps as there are different settings necessary in both cases.

As you run with 12.5Gbps your init command should look like this:

igd_eyescan init cX0Y28 gty_linerate_smaller10=0

With this the run should be possible.

------------------------------------------------------------------------------
Don't forget to reply, give kudo and accept as solution
------------------------------------------------------------------------------
607 Views
Registered: ‎12-18-2018

Re: GT-Debugger Eye-Qualification

Jump to solution

Thank you so much for your help.

 

Now it works as it should

0 Kudos
Newbie botmaster
Newbie
107 Views
Registered: ‎10-03-2019

Re: GT-Debugger Eye-Qualification

Jump to solution

I am working with a VCU108 and the other board with a xcvu13p, with 4 x 28.125Gbs links.

I used igd_eyescan init cX0Y28 gty_linerate_smaller10=0.
 
Then, I need to reset the GT to enable the eye scan. 
 

 
If I don't do this,the result will be wrong. 
 
 
I tried to reset the GT core or EYESCANRESET signal,but it was useless.It always remind me that "EYESCANRESET is not instrumented for the GT. The scan might not be valid and recalibration for the eye scan be necessary."
 
What should I do after this?
 
Thank you in advance for your help!
0 Kudos
Xilinx Employee
Xilinx Employee
72 Views
Registered: ‎10-19-2011

Re: GT-Debugger Eye-Qualification

Jump to solution

Hi @botmaster ,

first, this is a reply with a new topic to an already solved issue. Please open a new topic next time.

The eye scan routine needs to access the EYESCANRESET port at some point. For that, it needs access to it.
You need to instrument the port on the CHANNEL primitive for the scan to run properly.

You already selected the DRP for the CHANNEL to do eye scan. Just go down a bit further in the .do file and mark the line for EYESCANRESET with 'g'.
Then build the design again and try.

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