Answers Database

PAR: WARNING:basdp - The SITE "pin-out" specified in the .PCF file was not found in desgin


Record #2504

Problem Title:
PAR: WARNING:basdp - The SITE "pin-out" specified in the .PCF file was
not found in desgin



Problem Description:
Keywords: Prohibit, MD0, MD1, MD2, mode pins

Urgency: Standard

Problem Description:
User puts in following constraint in the UCF file:
CONFIG PROHIBIT = P32 ;

Par returns following error after parsing through PCF generated from UCF:
WARNING:basdp - The SITE "P32" specified in the .PCF file was not found in
   the design.	Please verify that:
   1. the specified SITE actually exists in the original design, and
   2. the specified SITE record in the .PCF file is spelled correctly.
WARNING:basdp - Ignoring constraint "PROHIBIT =  SITE "P32"; " because site
   not found


ERROR:baspw - The .pcf file contains errors/warnings.  PAR cannot proceed.


Solution 1:

In the error message, P32 is actually MD0(mode pin) for a PC84 package.
This is not a standard I/O. The Boundary Scan and Mode pins: TDI, TCK,
TMS, TDO, MD0, MD1, and MD2 are considered special purpose pins and will
only be used if the TCK, TDI, TMS, TDO, MD0, MD1, and MD2 pads are
specifically placed (instantiated) in the design.  The others mentioned:
HDC, LDC, INIT, DIN, DOUT do need to be prohibitted and will be used
indescriminately by the software.   M1 will issue an error message of the
type "unknown site" if a prohibit is placed on a Boundary Scan or Mode pin
site.  Essentially,  the user can be self assured that the M1 (Alliance)
software will only use the Boundary Scan or Mode pins for I/O when the
components are specifically placed (instantiated) in the design; there is
no reason to prohibit those sites.

PROGRAM, CCLK, and DONE cannot be prohibited since they are not I/Os.



Solution 2:

The P for P26 (or any other regular I/O) must be capitalized.



End of Record #2504