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 |
ChipPlanner |
ChipEditor |
Fusion |
X |
|
X |
|
ProASIC3E |
X |
|
X |
|
ProASIC3 |
X |
|
X |
|
ProASIC PLUS |
|
X |
X |
|
Axcelerator |
X |
|
X |
|
ProASIC |
|
X |
X |
|
eX |
|
|
|
X |
SX-A |
|
|
|
X |
SX |
|
|
|
X |
MX |
|
|
|
X |
3200DX |
|
|
|
X |
ACT3 |
|
|
|
X |
ACT2/1200XL |
|
|
|
X |
ACT1 |
|
|
|
X |
Use this constraint to assign one or more macros to a specific location. You can define the location using array co-ordinates.
By confining macros to one area, you can keep the nets connected to that area, resulting in better timing and better floorplanning. Sometimes, placing some macros at specific locations can also result in meeting timing closures.
You can use one or more of the following commands or GUI tools to assign a macro to a location:
PDC - set_location
GCF - set_location
ChipPlanner - Assigning logic to locations
ChipEditor - Assigning Logic