4.4.2 Checking a Block Instance Assignment to a Routing Region
MSVT checks the assignment of all instances of each block in the design to a routing region. The
regions must be defined with -route true to constrain routing. If a block
instance is not assigned to a routing region, MSVT lists the instance name in the
Following instances do not belong to any routing region section of the
report. If all instances are assigned to a separation region, the MSVT report omits this
section.
Note: This is an informational section meant to
identify instances that are not assigned to any region. The identified instances will not
be considered as errors.
Sample Design Constraints File
The following sample physical constraints code constrains a PolarFire design within separation routing regions.
Tip:
For more information about PDC constraints, see the PDC Commands User Guide.
PDC Constraints of a Sample Design for PolarFire
define_region -region_name Block1region -type exclusive -color 2143338688 -route true -push_place false -x1 456 -y1 195 -x2 1631 -y2 371
define_region -region_name Block2region -type exclusive -color 2143338688 -route true -push_place false -x1 1752 -y1 189 -x2 2435 -y2 377
define_region -region_name Block3region -type exclusive -color 2143338688 -route true -push_place false -x1 0 -y1 0 -x2 335 -y2 41 -x1 0 -y1 42 -x2 1067 -y2 161 -x1 804 -y1 0 -x2 1067 -y2 41
define_region -region_name Block4region -type exclusive -color 2143338688 -route true -push_place false -x1 1200 -y1 0 -x2 2351 -y2 158
define_region -region_name SMIPregion -type exclusive -color 2143338688 -route true -push_place false -x1 384 -y1 0 -x2 755 -y2 11
define_region -region_name IBR2_4 -type inclusive -color 2147442270 -route true -push_place false -x1 2148 -y1 105 -x2 2327 -y2 266
define_region -region_name IBR3_4 -type inclusive -color 2147442270 -route true -push_place false -x1 888 -y1 45 -x2 1463 -y2 98
define_region -region_name IBR1_4 -type exclusive -color 2143338688 -route true -push_place false -x1 1356 -y1 126 -x2 1499 -y2 245
define_region -region_name IBR1_3 -type inclusive -color 2147442270 -route true -push_place false -x1 636 -y1 102 -x2 851 -y2 239
define_region -region_name IBR1_2 -type inclusive -color 2147442270 -route true -push_place false -x1 1584 -y1 282 -x2 2027 -y2 362
assign_region -region_name Block1region -inst_name block1_0
assign_region -region_name Block2region -inst_name block2_0
assign_region -region_name Block3region -inst_name block3_0
assign_region -region_name Block4region -inst_name RESETN_ibuf
assign_region -region_name Block4region -inst_name block4_0
assign_region -region_name SMIPregion -inst_name pf_smip_0
assign_net_macros -region_name IBR2_4 -net_name block4_0_Y -include_driver true
assign_net_macros -region_name IBR3_4 -net_name block3_0_dataOut\[31\] -include_driver true
assign_net_macros -region_name IBR3_4 -net_name block3_0_dataOut\[30\] -include_driver true
assign_net_macros -region_name IBR3_4 -net_name block3_0_dataOut\[29\] -include_driver true
assign_net_macros -region_name IBR3_4 -net_name block3_0_dataOut\[28\] -include_driver truePDC Constraints of a Sample Design for SmartFusion2 and IGLOO2
-----------------------------------------------------------------------------------------------------------------------------------------
define_region -name UserRegion0 -type inclusive -color 8388736 -route YES -push_place YES 0 93 143 146
define_region -name UserRegion2 -type inclusive -color 12639424 -route YES -push_place YES 240 0 443 62
define_region -name UserRegion3 -type inclusive -color 15780518 -route YES -push_place YES 0 0 143 65
define_region -name UserRegion4 -type inclusive -color 16735838 -route YES -push_place YES 108 111 263 131
define_region -name UserRegion5 -type inclusive -color 975928 -route YES -push_place YES 324 21 371 119
define_region -name UserRegion6 -type inclusive -color 65535 -route YES -push_place YES 96 9 263 47
define_region -name UserRegion1 -type inclusive -color 32896 -route YES -push_place YES 240 96 443 146 276 201 359 206 324 138 347 206
assign_region UserRegion0 U_ST1/DCT8AAN1_0*
assign_region UserRegion0 U_ST1/INBUF_2*
assign_region UserRegion0 U_ST1/INBUF_3*
assign_region UserRegion0 U_ST1/IO_0*
assign_region UserRegion0 U_ST1/CFG0_GND_*
assign_region UserRegion1 U_B1/DCT_BUF_10_0*
assign_region UserRegion1 U_B1/INBUF_2*
assign_region UserRegion2 U_ST2/DCT8AAN2_0*
assign_region UserRegion2 U_ST2/INBUF_2*
assign_region UserRegion2 U_ST2/CFG0_GND*
assign_region UserRegion3 U_B2/DCT_BUF_12_0*
assign_region UserRegion3 U_B2/INBUF_2*
assign_region UserRegion3 U_B2/IO_0*
assign_region UserRegion3 U_B2/OUTBUF_0*
assign_net_macros UserRegion4 data1<* -include_driver YES
assign_net_macros UserRegion4 rdy1
assign_net_macros UserRegion5 data1r<* -include_driver YES
assign_net_macros UserRegion5 rdy2
assign_net_macros UserRegion6 data2<* -include_driver YES
assign_net_macros UserRegion6 rdy3 -include_driver YES
-----------------------------------------------------------------------------------------------------------------------------------------MSVT Output Report
MSVT reports all instances of the design that are not included in any routing regions, as shown in the following example.
Instances That Do Not Belong to Any Routing Region
-----------------------------------------------------------------------------------------------------------------------------------------
The following instances do not belong to any routing region:
====================================================================
PF_CCC_C0_0/PF_CCC_C0_0/pll_inst_0
REF_CLK_0_ibuf/U_IOIN
-----------------------------------------------------------------------------------------------------------------------------------------