Xilinx Constraints Guide

The following are not supported:
Chapter 4: Xilinx Constraints
• Dot extensions on ranges. For example, LOC=SLICE_X3Y5:SLICE_X5Y7.G
• The wildcard character for Spartan-3, Spartan-3A, Spartan-3E, Virtex-4 and Virtex-5
global buffers or DLL locations.
Location Types for CPLD Devices
CPLD devices support only the location type pin_name
where
Architecture Support
Applicable Elements
pin_name is Pnn for numeric pin names or rc for row-column pin names
Applies to all FPGA devices and all CPLD devices.
Sites
Propagation Rules
It is illegal to attach PROHIBIT to a net, signal, entity, module, or macro.
Syntax Examples
The following examples show how to use this constraint with particular tools or
methods. If a tool or method is not listed, you cannot use this constraint with it.
UCF Syntax
In a UCF file, PROHIBIT must be preceded by the keyword CONFIG.
For a single location:
CONFIG PROHIBIT=location;
For multiple single locations
CONFIG PROHIBIT=location1, location2, ... ,locationn;
For a range of locations:
CONFIG PROHIBIT=location1:location2;where
location is a legal location type for the part type
For more information, see Location Types for FPGA Devices and Location Types for CPLD
Devices below. For examples of using the location types, see the Location (LOC)
constraint. CPLD devices do not support the "Range of locations" form of PROHIBIT.
The following statement prohibits use of the site P45.
CONFIG PROHIBIT=P45;
The following statement prohibits use of the slice at the SLICE_X6Y8 site.
CONFIG PROHIBIT=SLICE_X6Y8;
PCF Syntax
For single or multiple single locations:
COMP “comp_name” PROHIBIT = [SOFT] “site_group”...”site_group”;
Constraints Guide
UG625 (v. 13.2) July 6, 2011 www.xilinx.com 225