When using the NoC INI to cross the DFX boundary, the INI supports either 1:N or N:1 connectivity only. This requires you to apply multiple INI interfaces to enable the MxN connectivity requirement across the DFX partition.
The following figure shows the 1:N NoC topology using Network-1 described previously. The NMU in the static region needs to access multiple NSUs in the dynamic region with different bandwidth requirements.
To achieve this topology in an IP integrator-based DFX design, you must enable three INI interfaces for the NoC IP inside the static region and dynamic region, as shown in the following figure.
In the following figure, S00_AXI (NMU) of the AXI NoC IP in the static region is connected to the M00_INI, M01_INI, and M02_INI interfaces using the Connectivity tab. Inside the dynamic region, corresponding INI interfaces (S00_INI, S01_INI, and S02_INI) are connected to one NSU each (M00_AXI, M01_AXI, and M02_AXI).
The following figure shows a single NMU connected to three INI interfaces in the static region.
The following figure shows three INI interfaces connecting to a single load (NSU) in the dynamic region.
The following figure shows the INI strategy set as Single load, Driver owns the path for the AXI NoC IP in the static region.
The following figure shows the INI strategy set to Single load, Driver owns the path for the AXI NoC IP inside the dynamic region.
The INI strategy is defined as Single load, Driver owns the path. As a result, the QoS setting is defined at the AXI NOC IP in the static region that has the NMU driver.
This topology is also possible in Network-2 shown in preceding sections, where the NMU is in the dynamic region and accesses multiple NSUs in the static region. The most common use case for this topology are PL peripherals in the dynamic region that access DDR memory controllers in the static region.
In the following example, the INI strategy must be set to Single Load, Driver owns the path, and multiple drivers (NMUs) must be added to connect to same INI.