Validating NoC - 2024.2 English - UG1387

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

Document ID
UG1387
Release Date
2024-12-18
Version
2024.2 English

The final step to the Modular NoC flow is to validate the NoC. This is achieved by running the validate_noc Tcl command. Prior to running this command, all BDs and IPs that are present in the design must be generated. The validate_noc command initiates RTL elaboration, applies NoC constraints from XDC, and invokes the NoC compiler. Additionally, the validate_noc command includes multiple embedded design rule checks (DRCs) to ensure the validity of the overall system-level NoC solution. After the validate_noc command is completed, the project-level NoC view is opened and the vivado.log reflects the NoC constraints being applied.

Figure 1. validate_noc Applying Constraints
Figure 2. Project-Level NoC View

In the project-level NoC view, you can see all the XPM NMUs/NSUs that were instantiated in the RTL are shown in the NoC Objects window.

Figure 3. NoC Objects Window Showing Instantiated XPMs

Alternately, you can open the project-level NoC view at any time by clicking the Project Manager in the Flow Navigator, select the Window menu, and click the NoC option.

Figure 4. Opening Project-Level NoC View
Note: The project-level NoC view appears the same as a BD level NoC view. If IP Integrator is selected in the Flow Navigator, then the BD NoC view is shown. If Project Manager is selected, then the project-level NoC view is shown. The BD NoC view shows a subset of the project-level NoC view. XPM NoC instances are only visible in the project-level NoC view. The project-level NoC view shows all NoC information in the design regardless of its origin. The BD level NoC view only shows the NoC information from the context of the BD.