Report NoC - Report NoC - 2026.1 English - UG906

Vivado Design Suite User Guide: Design Analysis and Closure Techniques (UG906)
Document ID
UG906
Release Date
2026-06-23
Version
2026.1 English

The report_noc command captures all NoC usage regardless of design entry method. You can generate this report at any stage after synthesis. It provides a comprehensive record of NoC usage, NoC settings, and related NoC details.

The NoC report generates multiple tables. To cross-reference tables, use NoC Path ID as a searchable index. The tool generates the following tables when applicable:
Table 1. Quality of Service
Header Description
Locked Indicates whether the path has locked routing and the tool cannot modify it.
Phase Optional scheduling phase assigned to this path for time-division traffic control.
Write Traffic Class QoS traffic class for write transactions. Common values are best effort (BE), isochronous (ISOC), and low latency (LL).
Write B/W Req. Requested write bandwidth for this path, in Mb/s.
Write B/W Act Actual write bandwidth allocated by the tool after routing, in Mb/s.
Write Overhead Additional write bandwidth consumed by protocol overhead (for example, AXI write response channel). Expressed in Mb/s. Total write bandwidth used = actual + overhead.
Write Av. Burst Average write burst length, in beats, used to compute bandwidth requirements.
Write Data Width Bit width of the write data channel for this NoC path. Bandwidth is expressed in Mb/s.
Read Traffic Class QoS traffic class for read transactions. Common values are BE, ISOC, and LL.
Read B/W Req Requested read bandwidth for this path, in Mb/s.
Read B/W Act Actual read bandwidth that the tool allocates after routing, in Mb/s.
Read Av. Burst Average read burst length, in beats, used to compute bandwidth requirements.
Read Data Width Bit width of the read data channel for this NoC path. Bandwidth is expressed in Mb/s.
Source Hierarchical cell path of the NoC master unit (NMU) that originates traffic on this path.
Target Hierarchical cell path of the NoC slave unit (NSU) that receives traffic on this path.
Table 2. Shared Physical Channels
Header Description
Protocol Data transfer protocol used on this path, for example AXI memory-mapped (AXI_MM).
# Shared Channels Number of other NoC paths that share physical routing channels with this path.
Shared Channels Identifier The NoC Path ID of each peer path that shares physical routing channels with this path.
Shared Channels Protocol Protocol used by each peer path that shares channels with this path.
Source Hierarchical cell path of the NMU that originates traffic on this path.
Target Hierarchical cell path of the NSU that receives traffic on this path.
Shared Channels Source NMU cell path of the peer path that shares physical routing channels with this path.
Shared Channels Target NSU cell path of the peer path that shares physical routing channels with this path.
Table 3. Initial Boot Paths
Header Description
Source Hierarchical cell path of the NMU that originates traffic on this boot path, for example a NOC2_NMU128_INST connected to an AXI or RPU slave port.
Target Hierarchical cell path of the NSU or memory controller endpoint that receives traffic on this boot path, for example a DDRMC5_COMP instance within a DDR5 memory controller.
Table 4. Apertures
Header Description
NSU Hierarchical cell path of the NSU (NoC Slave Unit) that owns the address aperture.
Aperture(s) Base address and size of the memory aperture mapped to this NSU, for example 0x80100000000 64K. Multiple apertures can be listed per NSU.
Connected NMUs Hierarchical cell path(s) of the NMU instances that are routed to this NSU through the listed aperture. Multiple NMUs can share the same NSU aperture.
Table 5. Location, Address, SLR
Header Description
Type Functional type of the NoC endpoint, indicating whether it is an NMU or NSU and which subsystem it belongs to, for example PL-attached NoC master unit (PL_NMU_2) or PMC-attached NoC master unit (PMC_NMU_2).
Path Hierarchical cell path of the NMU or NSU instance in the design.
Protocol Data transfer protocol used by this endpoint, for example AXI_MM.
Locations Physical placement site of the endpoint on the device, for example NOC2_NMU512_X0Y3.
Base Address Base address of this endpoint's configuration or control register space in the device address map, expressed as a hexadecimal value.
PMC Alias Offset Address offset applied by the PMC alias window. Adding this offset to the base address yields the absolute address, expressed as a hexadecimal value.
Absolute Address Full system address of this endpoint, equal to base address plus PMC alias offset, expressed as a hexadecimal value.
SLR Super logic region index where this endpoint is physically located. This field is relevant for multi-die or stacked-silicon devices.

Other tables capture exclusive routing groups, separate routing groups, remaps, virtual channels, and DFX ownership.