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 |
Fusion |
X |
|
X |
ProASIC3E |
X |
|
X |
ProASIC3 |
X |
|
X |
ProASIC PLUS |
|
X |
X |
Axcelerator |
X |
|
X |
ProASIC |
|
X |
X |
eX |
|
|
|
SX-A |
|
|
|
SX |
|
|
|
MX |
|
|
|
3200DX |
|
|
|
ACT3 |
|
|
|
ACT2/1200XL |
|
|
|
ACT1 |
|
|
|
Use this constraint to assign one or more macros to a specific region.
By confining macros to one area, you can keep the nets connected to that area, resulting in better timing and better floorplanning.
For ProASIC3/E and Axcelerator devices, you can use the define_region PDC command to create a region, and then use the assign_region PDC command to constrain a set of existing macros to that region.
For ProASIC PLUS and ProASIC, you can use the set_location GCF command to both create a region and constrain an existing set of macros to it at the same time. To define a region with the set_location command in a GCF file, you must specify the array coordinates for a rectangular area, for example, x1, y1, x2, y2.
You can also use the MultiView Navigator tool to create regions for any of the supported families.
You can use one or more of the following commands or GUI tools to assign a macro to a region:
PDC - assign_region
GCF - set_location
ChipPlanner - Assigning a macro to a region