03-10-2014 11:06 AM - edited 03-10-2014 11:18 AM
I am working on a design that someone else had previously instantiated Aurora into. I was doign some advancements that used too many resources, so I decided to put some paramaters around the aurora stuff to allow me to test without instantiating it, but not change the code. That seems to throw things for a loop.
What I think the issue is, is that the aurora clock input/output pins are on particular pins, and the tools are expecting something of them. I was able to get through most of the issues by adding the following statements (just to make the tools happy):
wire GTXQ1_CLK; IBUFDS_GTXE1 IBUFDS_GTXE1_CLK1 ( .I (GTX_CLK_P2), .IB (GTX_CLK_N2), .CEB (1'b0), .O (GTXQ1_CLK), .ODIV2 () ); wire RXin1; wire RXin2; IBUFGDS IBUFGDS1 ( .I(SFP1_RXP), .IB(SFP1_RXN), .O(RXin1) ); IBUFGDS IBUFGD2 ( .I(SFP2_RXP), .IB(SFP2_RXN), .O(RXin2) );
Everything is good except that the output pins are now failing MAP (SFP1_TXP, SFP1_TXN, SFP2_TXP, and SFP2_TXN). Is there anything I can do to those pins to make the tools happy?
The error I get looks like this:
Pack:1107 - Pack was unable to combine the symbols listed below into a single IOBS component because the site type selected is not compatible. Further explanation: The component type is determined by the types of logic and the properties and configuration of the logic it contains. In this case an IO component of type IOBS was chosen because the IO contains symbols and/or properties consistent with differential slave usage. Please double check that the types of logic elements and all of their relevant properties and configuration options are compatible with the physical site type of the constraint. Summary: Symbols involved: PAD symbol "SFP1_TXN" (Pad Signal = SFP1_TXN) SlaveBuffer symbol "OBUFDS1/SLAVEBUF.DIFFOUT" (Output Signal = SFP1_TXN) Component type involved: IOBS Site Location involved: Y2 Site Type involved: OPAD
03-10-2014 12:44 PM - edited 03-10-2014 12:47 PM
I think that you have removed the Aurora core and are attempting to replace with an IBUFDS for the RXP/RXN and an OBUFDS for the TXP/TXN. You cannot do this as the only valid connection the dedicated MGT pins is the MGT.
03-10-2014 01:41 PM
Pack needs the context of the GT connectivity to create the correct component type of OPAD instead of an IOB. The error occurs because an IOB is a mismatch for the OPAD site.
03-11-2014 04:00 AM - edited 03-11-2014 04:01 AM
I have removed the core (basically put it in a parameter check that never resolves), and just wanted to tools to run. It complained about the TXP/TXN, so I did indeed toss some OBUFDS in there to try to make the tools happy (which obviously didn't work).
Is there something I can do to make the tools have (re the TXP/TXN pins) without the core being there (maybe something the equivelent of the IBUFDS_GTXE1)? (or maybe a way to wrap the output pins in the ucf in the parameter check)?
03-11-2014 08:35 AM - edited 03-11-2014 08:35 AM
I think that the only way to resolve this is to remove the ports from the top level design and comment out the UCF.