When the NoC path crosses a DFX boundary, the specific path can be owned by the static region or dynamic region. Path ownership defines which segment of the path defines the QoS for the path. It also determines how much of the NoC is reprogrammed when the dynamic region is reprogrammed during runtime. If the static region owns the path, the entire NoC path spanning the reconfigurable partition (RP) is not reprogrammed during reconfiguration and must remain the same for all reconfigurable modules (RMs). If the dynamic region owns the path, the entire NoC path from NMU in the dynamic region to NSU in the static region is reprogrammed during reconfiguration.
Below are the different ownership possibilities for NoC paths crossing RP boundaries based of the virtual NoC interface mode.
Path ownership is based on the virtual NoC interface mode and the NMU/NSU types in the static and dynamic portions of a DFX design.
Static Region | Dynamic Region | Virtual NoC Interface Mode | Ownership |
---|---|---|---|
NMU | NSU | VNMU | Invalid use case |
NMU | NSU | VNSU | Static owns the path |
NSU | NMU | VNMU | Static owns the path |
NSU | NMU | VNSU | Dynamic owns the path |
The get_property primary [get_noc_connections]
Tcl command can be used
to identify the segment of the NoC connection that owns the path. This is the segment of
the path where the QoS for the connection must be specified.