The Design Configuration section is divided into two tables. The first table has information about the design stage, including whether the stage is a parent or child run. The static information is generated using the standard DFX flow or the Abstract Shell flow. Each RP is assigned a unique Partition ID (RP1, RP2, etc.), which is used consistently across all report tables. The second table shows details on each RP.
Figure 1. Design Configuration Table
| Column | Description |
|---|---|
| Reconfiguration Partition ID | Unique ID assigned to RP |
| Instance Name | RM cell name |
| Pblock Name | Name of RP Pblock |
| Disjoint Pblock | Is the RP Pblock disjoint? Yes (Y) or No (N) |
| # Child Pblock | Number of child Pblocks under primary region for disjointed Pblocks |
| Sub-Child Pblock | Is a sub-child Pblock present? Yes (Y) or No (N) |
| # Pblocks for QoR | Number of child Pblocks under primary region for disjoint Pblock. Number of child Pblocks under non-disjoint Pblock with parent Pblock as an RP Pblock. |
| Boundary Pin Count | Number of boundary pins of the RM |
| Number of Boundary Clocks | Number of boundary clocks of the RM |
| Placement Footprint | Number of tiles included in placement footprint of RM |
| Routing Footprint | Number of tiles included in routing footprint of RM |
Note: Child Pblocks are disjoint Pblocks with primary
and secondary regions. Sub-child Pblock are child Pblocks under the primary region
Pblock of a disjointed Pblock. For non-disjoint Pblocks, sub-child Pblocks are child
Pblocks with the RP Pblock as the parent Pblock.