Both isolated modules and reconfigurable partitions require Pblocks to identify resources to contain these respective parts of the design. You can follow requirements for the respective module type as documented in each user guide. The combined IDF+DFX solution adds more design rule checks (DRCs); run these interactively as you build the floorplan and watch for critical warnings as the implementation flow is run.
The most fundamental rule is that the Pblock ranges for any isolated module within a reconfigurable partition be completely contained within the RP Pblock. Standard fence rules apply regardless of where the isolated module Pblock exists. The fence can be either inside or outside of the RP Pblock.
This collection of RMs for the one reconfigurable partition in the design might have different internal floorplans for the isolated regions contained within, but the interface port list must remain consistent, per DFX rules. The two RMs shown in the following figures are legal and no extra guidance is needed to account for the different sizes of isolated modules within RM1 and RM2.
Nested Pblocks within an isolated Pblock are supported and can be used to meet timing closure requirements. However, the following Pblock configurations are not supported:
- An isolated Pblock nested inside another isolated Pblock (nested IDF Pblocks)
- A DFX Pblock nested inside another DFX Pblock (nested DFX Pblocks)
- A DFX Pblock nested inside an isolated Pblock
Nested Pblocks inherit the properties of their parent Pblock. For example, if IS_SOFT is set to FALSE on the parent Pblock, the same setting is inherited by the nested Pblocks. Additionally, net splitting is not supported when either the driver or the load resides within a nested Pblock. In such cases, net splitting fails.