Virtual NoC Interfaces - Virtual NoC Interfaces - 2026.1 English - UG1387

Versal Adaptive SoC Hardware, IP, and Platform Development Methodology Guide (UG1387)

Document ID
UG1387
Release Date
2026-07-22
Version
2026.1 English

DFX designs use virtual NoC interfaces to segment NoC connections. This enables:

  • NoC connections to be split between the static and dynamic regions of the design
  • Adding the address apertures on the boundary of a DFX region

The NMU or NSU in the static region of the design creates a NoC connection to a virtual interface. A second connection exists on the dynamic region connecting a virtual NoC interface to the corresponding NMU or NSU. To complete the segmented connection, the two virtual interfaces must share a common name.

Separate the XDC files for such a design. The static XDC must contain the static connection from the NMU or NSU to the virtual interface. The XDC file scoped to the reconfigurable module (RM) must create the virtual interface with the same name. It must connect the virtual interface to the NSU or NMU in the dynamic region.

The example below shows the creation of the virtual NMU in Top and RM level XDCs.

In Top XDC:

set vnmu_1 [create_noc_interface -mode vnmu <hirearchy>/<virtual_intf_name>]

In RM XDC (scoped to the RM):

set vnmu_1 [create_noc_interface -mode vnmu <virtual_intf_name>]
Note: The <virtual_intf_name> must be the same in the XDC files for the path to be created.