GTX transceivers

Thanks, that was quite helpful.  For the aid of anyone else reading this later, can you post the Vivado script command you used to generate that list?

I'm going to investigate something, but this is bothering me a lot:
RXUSRCLK2_FREQt97,680664
RXUSRCLK_FREQt97,680664

If you have a 250MHz input, I would expect that to be somewhere closer to 250Mhz.  You can see in Video 103 at 03:26 that what I see on my board, when I run at 250Mhz input.  I am seeing 234.424Mhz.

Do you have a high speed oscilloscope or other way of measuring the clock?  If you remove your PicoZed, you should be able to get a probe on the capacitor pads for C153/C154 located near the silkscreen 2 on JX3.  These capacitors should have had resistors added at this time (from the PicoZed FMC Carrier Card Rev C Errata located http://picozed.org/support/documentation/4701 ).

It seems to me that without explaining this, we do not need to go much farther, since the chip is reporting that it is not able to pull the clock out of the data.  The transceivers use a clock embedded into the data.  97Mhz is WAY off from where it needs to be to function properly.

The other thing that is bothering me, you have tried this on multiple versions of Vivado, with two different boards, yet you see the same result.  It almost feels like your PC might have some kind of Virus protection or something that did not allow Vivado to install properly.  Or, we have had the Vivado install file not download properly, but seem like it installed properly.  To check this, we always validate the downloaded file with a check-sum validation.  Typically we recommend this tool:
https://www.fourmilab.ch/md5/

If you can check your install source file, as well as make sure that NO anti-virus or other programs are running this might help.  You can also try installing a fresh copy of Vivado on a second PC if you can.  That might be the fastest, instead of re-installing.  Again, make certain you do not have any anti-virus or other types of programs running, or you get your company's IT department to do this for you following the above rules.  This is of course AFTER validating the source install file.

If you are watching the Vimeo version of the video - make sure you click the HD icon in the lower right of the player, so you can read the words in the video.

That became a bit long, here is a bullet list for you to try this time:

*ensure all modifications are performed per PicoZed FMC Carrier Card Rev C Errata
*validate the MD5 of the install SOURCE file you downloaded for Vivado
*ensure that Vivado was installed WITHOUT Anti-virus or other protection
*ensure that your IS department has granted you the proper permissions to allow you to use all of Vivado
*validate the clock using capacitor pads located near the silkscreened 2 of JX3
**for ease of use, I believe the U12 part will also output it's frequency on J15/J16 if that is easier to measure from to validate U12, however measuring the capacitor pads will give you what the PicoZed is seeing

Thanks, that was quite helpful.  For the aid of anyone else reading this later, can you post the Vivado script command you used to generate that list?

I'm going to investigate something, but this is bothering me a lot:
RXUSRCLK2_FREQt97,680664
RXUSRCLK_FREQt97,680664

If you have a 250MHz input, I would expect that to be somewhere closer to 250Mhz.  You can see in Video 103 at 03:26 that what I see on my board, when I run at 250Mhz input.  I am seeing 234.424Mhz.

Do you have a high speed oscilloscope or other way of measuring the clock?  If you remove your PicoZed, you should be able to get a probe on the capacitor pads for C153/C154 located near the silkscreen 2 on JX3.  These capacitors should have had resistors added at this time (from the PicoZed FMC Carrier Card Rev C Errata located http://picozed.org/support/documentation/4701 ).

It seems to me that without explaining this, we do not need to go much farther, since the chip is reporting that it is not able to pull the clock out of the data.  The transceivers use a clock embedded into the data.  97Mhz is WAY off from where it needs to be to function properly.

The other thing that is bothering me, you have tried this on multiple versions of Vivado, with two different boards, yet you see the same result.  It almost feels like your PC might have some kind of Virus protection or something that did not allow Vivado to install properly.  Or, we have had the Vivado install file not download properly, but seem like it installed properly.  To check this, we always validate the downloaded file with a check-sum validation.  Typically we recommend this tool:
https://www.fourmilab.ch/md5/

If you can check your install source file, as well as make sure that NO anti-virus or other programs are running this might help.  You can also try installing a fresh copy of Vivado on a second PC if you can.  That might be the fastest, instead of re-installing.  Again, make certain you do not have any anti-virus or other types of programs running, or you get your company's IT department to do this for you following the above rules.  This is of course AFTER validating the source install file.

If you are watching the Vimeo version of the video - make sure you click the HD icon in the lower right of the player, so you can read the words in the video.

That became a bit long, here is a bullet list for you to try this time:

*ensure all modifications are performed per PicoZed FMC Carrier Card Rev C Errata
*validate the MD5 of the install SOURCE file you downloaded for Vivado
*ensure that Vivado was installed WITHOUT Anti-virus or other protection
*ensure that your IS department has granted you the proper permissions to allow you to use all of Vivado
*validate the clock using capacitor pads located near the silkscreened 2 of JX3
**for ease of use, I believe the U12 part will also output it's frequency on J15/J16 if that is easier to measure from to validate U12, however measuring the capacitor pads will give you what the PicoZed is seeing

Hi Daniel
I have found the reason for  the empty BER Column.  I changed the Regional setting to US notation in my S.O and I got this problem  SOLVED.

*  However, when I measured the clock frequency I noticed  that without PicoZed, no clock signal appears in J15/J16, I only got clock when the PicoZed  is connected to the FMC Carrier Card.  IS IT CORRECT?, according with the schematics should be like that.

*  When I measured the frequencies --J15/J16-- I got this results:

Freq (table)    Freq (oscilloscope)
62.5 Mhz  ---   62.5 Mhz
100  Mhz  ---   150  Mhz
125  Mhz  ---   83.3 Mhz
200  Mhz  ---   no signal
250  Mhz  ---   250.2  Mhz  

I didnu00B4t change C153/C154 capacitors, because I found it quite difficult.  These can be the reason for having such frequency deviations ???.

* Another serious problem is that still I am getting

RXUSRCLK2_FREQt97,680664
RXUSRCLK_FREQt97,680664

with a 250MHz input, which means no proper transceiver functionality. 


I have tested the same using 3 boards (Picozed + FMC) with the same results.

Thanks for your kindly help.