07-01-2019 08:40 AM
Hi,
I'm working on a ZynqMP-based SoM, on an in-house board, and I'm trying to use the GTR tranceiver to act as USB3 device (5 Gbps). As my software works on reference boards and not on my own, I suspect signal integrity issues. Unfortunatelly when USB3 is failing, the USB stack falls back to USB2, making hard to measure Signal Integrity on GTR lines.
How can I set the GTR to continuously send any test packet that would allow me to check the quality of my physical link ? Debug registers are'nt documented in UG1087.
Thanks
07-03-2019 09:50 AM
A good way to see the signal integrity here would be IBERT for GTR. There is a tutorial in UG936 - Lab 10 on page 172 that will walk you through how to do this. You would then take a look at each eye to compair. It get an apples to apples comparison you may want to force the good board into USB2. I suspect this will still show a good/bad eye if signal integrity is your issue.
The GTR are not like normal transcivers. Many of the tuning registers are not user accesible and not tunable like you would normaly find on our transcivers. Much of the tuning is handled by your protocol.
Below is our GTR debugging guide. It will walk you through some other debug steps and dumps that might be valuable to debugging.
For SI issues i start with the clocking. Check that your Clock meets the design requirements, and measure it on a scope, if you can, to see if its doing what you expect within its specs.
http://www.xilinx.com/support/answers/69483.htm
07-03-2019 09:50 AM
A good way to see the signal integrity here would be IBERT for GTR. There is a tutorial in UG936 - Lab 10 on page 172 that will walk you through how to do this. You would then take a look at each eye to compair. It get an apples to apples comparison you may want to force the good board into USB2. I suspect this will still show a good/bad eye if signal integrity is your issue.
The GTR are not like normal transcivers. Many of the tuning registers are not user accesible and not tunable like you would normaly find on our transcivers. Much of the tuning is handled by your protocol.
Below is our GTR debugging guide. It will walk you through some other debug steps and dumps that might be valuable to debugging.
For SI issues i start with the clocking. Check that your Clock meets the design requirements, and measure it on a scope, if you can, to see if its doing what you expect within its specs.
http://www.xilinx.com/support/answers/69483.htm