Physical ownership relates to Isolated Regions (Pblocks)
- No user logic component can be used if it is not physically owned
by an isolated Pblock.
- Physical ownership is defined by the addition of the available components/PUs to the isolated Pblock definition in the XDC file/ Pblock drawn using Vivado GUI.
- A Pblock is called isolated Pblock if it is mapped to an isolated module.
-
resize_Pblock
constraint allows a range of slices placed in the Pblock to be used by the developer.
- Global logic, while not typically owned by any isolated logic, must be associated with any isolated Pblock, except for BUFGs and BUFHs. If the global logic is part of an isolated module and not a BUFG or BUFH, it must be associated with the isolated Pblock of that isolated module. Additionally, remember to exempt global logic using HD.ISOLATED_EXEMPT property.