04-12-2018 03:45 PM - edited 04-12-2018 03:52 PM
when xilinx IP core (in my case PCIE gen2 lane 1 for kintex 7 series xc7k325t) hierarchy is expanded all the RTLs/XDC code are seen in read only mode in vivado. I would like to know if these RTLs/XDC code are copied into new RTL/XDC files and edit it as per need and then use it with design. Does it work same as IP core? OR there will be restriction or license problem?
I am in trouble in my case when I generate PCIE IP core it automatically take QPLL of Transceiver bank but I want to use CPLL for this because QPLL and common of the same transceiver bank are already occupied by 10G. Is there any suggestion?
04-13-2018 08:37 AM
Specifically for the problem you are trying to solve, in 7-series, I would recommend you look at the "Shared Logic" option in the PCIe IP core. There is a way to share the GT common between two cores, without having to manually edit the locked core itself. The option pulls the GT common externally, then it can be hooked up to both cores needing it. This is described in detail in here:
04-14-2018 11:58 AM - edited 04-14-2018 12:04 PM
The link you provided is the exact requirement for me but unfortunately only with simulation result and I am looking for edited code. Is there also edited code available somewhere to download?
Here are some info before I ask my question:
1.In the link you provided it is mentioned that:
Generally one core file set is left alone while the other is edited then added to the original unedited core design. One COMMON block is needed per quad. Remove the additional COMMON block.
in page 319: The Channel PLL (CPLL) is recommended for Gen1 and Gen2 speeds. The Quad PLL (QPLL) is required for Gen3 speeds.
Each GT channel has the circuitry to select the reference clock and PLL that it will use.
I am intending to left 10G and edit PCIE. I am using gen2 pcie so as per point 2 and point 3 I mentioned here can I even completely remove pcie common and left pcie core inputs from common (QPLLOUTCLK, QPLLOUTREFCLK and QPLLOCK ) unconnected? Does it work? or need some more works?
P.S. Both protocols have different reference frequency 156.25 MHz and 100 MHz.
04-16-2018 09:02 AM