The following table shows which families support this constraint and which file formats and tools you can use to enter or modify it:
Families |
PDC |
GCF |
PIN |
PinEditor |
Fusion |
X |
|
|
X |
ProASIC3E |
X |
|
|
X |
ProASIC3 |
X |
|
|
X |
ProASIC PLUS |
|
X |
|
X |
Axcelerator |
X |
|
|
X |
ProASIC |
|
X |
|
X |
eX |
|
|
X |
X |
SX-A |
|
|
X |
X |
SX |
|
|
X |
X |
MX |
|
|
X |
X |
3200DX |
|
|
X |
X |
ACT3 |
|
|
X |
X |
ACT2/1200XL |
|
|
X |
X |
ACT1 |
|
|
X |
X |
Use this constraint to set the location of a pin.
For ProASIC3/E and Axcelerator, you can use the set_io command in a PDC file to assign I/Os to pins as well as set the attributes of an I/O. For ProASIC PLUS and ProASIC, you can use the set_io command in a GCF file to assign package pins to I/O ports or to locate I/O ports at a specified side or location of a device. For earlier families, you can use a PIN file to set the location of a pin.
You can use one or more of the following commands or GUI tools to assign an I/O to a pin:
PDC - set_io
GCF - set_io
PinEditor (MVN) - Assigning pins
PinEditor (non-MVN) - Assigning pins
Note: You can also set the location of a pin using the pin_assign command in a Tcl script.