Answers Database


M1.5i/2.1i: Timing: Instantiated TDO Pad Conflicts With UCF Constraint Causing error baste:263


Record #6662

Product Family: Software

Product Line: Merged Core

Product Part: Timing

Problem Title:
M1.5i/2.1i: Timing: Instantiated TDO Pad Conflicts With UCF Constraint Causing error baste:263



Problem Description:
Urgency: Standard

General Description:
When the TDO pin either has a location constraint placed
upon it, either as a schematic attribute or in a .ucf file, the
following errors could occur:

ERROR:OldMap:69 - LOC constraint "P76" on TDO symbol
   "$I1" (pad signal=TDOOUT) not supported.


In M1.5.29i, when a TDO buf is instantiated in VHDL (FPGA Express Flow) and the TDO pin is also lo cked in the .ucf file the following fatal error occurs:

ERROR:baste:263 - The LOC constraint "P76" (a TESTDATA location) is not valid
    for symbol "M2A<4>.PAD" (pad signal=M2A<4>), which is being mapped to the
    following site types:
         CLKIOB
         IOB

When a schematic test case was run in M1.5.29i, with the constraint on the schematic as a pad attrib ute, the
following fatal error occurred:

ERROR:baste:16 - LOC constraint "P76" on TDO symbol "$I1" (pad signal=TDOOUT)
    not supported.

When the constraint was put in a ucf file in M1.5.29i (and removed from the pad attribute on the sch ematic)
the following fatal error occurred:

ERROR:baste:16 - LOC constraint "P76" on TDO symbol "$I1" (pad signal=TDOOUT)
    not supported.




Solution 1:

To avoid the error, do not put a loc constraint on the TDO pin,
since this pin is already locked down to a specfic location on
the device..




End of Record #6662 - Last Modified: 07/14/99 09:01

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!