05-05-2014 05:27 AM
I have generated a Chipscope IBERT core for one of the GTX lane (MGT1_117) in Kintex-7 FPGA using ISE version 14.6 coregen tool. I am not interested in using GTXE2_COMMON (Quad PLL) primitive, as my lane rate is very low which is 1.25Gbps. So i have un-checked the QUAD PLL option while generating the core. But still GTXE2_COMMON primitive is getting instantiated from the corresponding GTX_QUAD_117. I confirmed the same by importing implemented design to FPGA editor.
Can anybody suggest, how do i avoid GTXE2_COMMON primitive inference in IBERT core!
Thanks in Advance!
05-05-2014 10:40 PM
05-05-2014 11:03 PM
Have a look at the below AR to know why a GT_common primitive is needed
05-05-2014 11:27 PM
Thanks for your response and i understand from FPGA editor that refclk is routed to the channel through CPLL only. Then why GTXE2_COMMON primitive is unnecessarily getting instantiated??
In my design, i have to enable Two channels in the same QUAD. One channel using IBERT core and the second channel using SDI core. And i wanted to integrate both the channels to have a common FPGA image. SDI core definitely requires GTXE2_COMMON in my design. Hence the implementation tool throwing an error saying that, COMMON primitives are over mapped. How do i resolve this issue?
05-06-2014 01:58 AM
05-06-2014 02:23 AM
Actually i have already decided to modify the IBERT wrapper file. When i look into the top level wrapper, i understood that source codes are not provided and instead ".NGC" file is provided. Then how do i play with wrapper file when it is in ngc format?
05-07-2014 03:21 AM
Do you suggest any other way to resolve this issue?
05-07-2014 03:41 AM
05-07-2014 03:42 AM
05-09-2014 03:06 AM
Thanks for your suggestion. But how do i use COMMON block of IBERT with other cores. For that, i need to bring out the "QPLLOUTCLK" from IBERT to connect QPLLINCLK for my custom GTX core, right?
The reason why i wanted to have IBERT in my main design is, i don't want any FPGA interfaces left un-tested in the final FPGA image, which i am gonna release to my customer. :)