Use the following checklist to help the NoC Compiler to create a solution that satisfies your traffic specifications:
- Are the Quality of Service requirements in your Traffic Specification
specified as accurately as possible? Refer to Quality of Service.
- Are LOW LATENCY and ISOCHRONOUS classes assigned to the appropriate nets? (Refer to Traffic Classes.)
- Are bandwidths assigned as accurately as possible? These can be over-constrained but must not be under-constrained. Refer to Read and Write Bandwidth.
- Are AXI masters transferring data using bursts that are multiples of the NoC chop size, in order to minimize the impact of NoC overhead? Refer to Read and Write Bandwidth.
- Do the average burst lengths assigned in the NoC’s Advanced QoS tab accurately reflect the burst lengths of the AXI masters? Refer to AXI Average Burst Length.
- Are you using Exclusive Routing Groups only for their intended purpose? That is, functional safety, not to guarantee bandwidth. Refer to Exclusive Routing Groups.
- Are you using Separate Routing Groups only for their intended purpose? That is deadlock avoidance. Refer to Separate Routing Groups.
- Are you aware of the impact of distance on latency through the NoC? Refer to Latency as a Function of NMU to NSU.
- Are you using Exclusive Routing Groups on Multi-SLR devices and aware of how they can conflict with the Boot Paths? Refer to Multi-SLR NoC Boot Paths.
- Are you using Versal features/IP which can place additional demands on NoC resources? (Debug Hub/CPM). Refer to 'Under-the-Hood' NoC Usage / NoC and Debug Infrastructure.
- Did you carefully review the NoC Compiler results, including warning and error messages Did you ensure that all requirements were met?