When the NoC path crosses a DFX boundary, the static region or dynamic region can own the specific path. Path ownership defines which segment of the path defines the QoS for the path. It also determines how much of the NoC to reprogram when the system reprograms the dynamic region at runtime.
If the static region owns the path, it does not reprogram the entire NoC path spanning the reconfigurable partition (RP) during reconfiguration. It 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. This reprogramming occurs during reconfiguration.
Below are the different ownership possibilities for NoC paths crossing RP boundaries based of the virtual NoC interface mode.
The virtual NoC interface mode and the NMU/NSU types determine path ownership 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 |
Use the get_property primary
[get_noc_connections] Tcl command to identify the segment of the NoC
connection that owns the path. Specify the QoS for the connection in this segment of the
path.