Version Found: v1.3
Version Resolved and other Known Issues: See (Xilinx Answer 40469).
Xilinx recommends enabling the OOB clocking mode option in the integrated block wrapper. This enables a separate 62.5 MHz clock input on the CLKSRSVD0 input pin of the MGT that is used to clock the OOB circuitry inside the MGT instead of the input reference clock. This clock needs to be a low frequency clock.
If the reference clock frequency used is 250 MHz, this will be needed, otherwise the link will not be stable due to the MGTs incorrectly signaling electrical idle to the block. However, Xilinx recommends enabling this mode for all frequencies and will be the default starting with the v1.5 release.
To work around this issue (can only be applied when the core is generated for General ES), please follow these steps:
1. Edit thexilinx_pcie_2_1_ep_7x.v file in the example_designdirectory to add the following wire. This connection is missingwhich causes the clock to not connect from the external clocking module instantiated in this file to the underlying wrapper files.
2.In the generated core's source directory, edit the file < generated core name >_gt_top.v and enable the PCIE_OOBCLK_MODE parameter. Find the instantiation of the pipe_wrapper_i module (around line 336) and change the PCIE_OOBCLK_MODE parameter to 1.
If the generated core selected VHDL for the wrapper, the connection is already present in the top level file. The only change needed is in the< generated core name >_gt_top.vhd file. In the file, find the instantiation of the pipe_wrapper_i file (around line 602) and change the PCIE_OOBCLK_MODE generic from 0 to 1.
In the v1.4 or v1.3 release, if the PCIE_OOBCLK_MODE is enabled, then the core will not link train during simulation. This is only a simulation problem and hardware works fine. For simulation, change the parameter back to 0 and regardless of the reference clock speed, there will be no issue during simulation if not using the extra OOB clock.
NOTE: "Version Found" refers to the version the problem was first discovered. The problem might also exist in earlier versions, but no specific testing has been performed to verify earlier versions.
05/01/2012 - Initial release
05/11/2012 - Added information that this is only for GES