When a NoC path crosses a DFX boundary, the specific path can be owned by the static region or the dynamic region. Static ownership of a NoC path ensures that the NoC solution for that boundary NoC path is locked down after initial parent implementation and the same NoC solution is honored and reused for subsequent child implementations. The following figure demonstrates the different ownership possibilities for DFX boundary NoC paths.
- When an NMU is in the static region drives an NSU in a dynamic region, the only supported ownership is static ownership.
- When an NMU is in a dynamic region drives an NSU in the static region, you can choose the path to be either static-owned or dynamic-owned. AMD recommends static ownership if there are more than one reconfigurable partitions in the design.
- Due to the presence of two connections depicting the specific boundary NoC path –
one between the virtual NoC interface and the NoC endpoint in the static region, and
the other between the virtual NoC interface and the NoC endpoint in a dynamic region
– the primary property has been introduced for the NoC connection to indicate
ownership.
get_property primary [get_noc_connections <connection_name>]
Figure 1. Boundary NoC Path Ownership Options