The Vivado IP integrator invokes the NoC Compiler during block design validation to generate a NoC placement and routing solution to meet Quality of Service (QoS) requirements. If the solution from IP integrator does not sufficiently meet design implementation requirements, the NoC Compiler might be invoked during design placement to generate a new solution to meet the implementation requirements.
Figure 1. NoC Compiler Flow
Following are implementation requirements that might cause the NoC Compiler to be invoked during design placement:
- Physical location or Pblock constraints applied to the Programmable Logic (PL) that influences NoC NoC Master Unit (NMU)/ NoC Slave Unit (NSU) placement
- Resolution of the NoC interface between CIPS and NoC for proper assignment to the targeted device
- Top-level port assignment of DDR memory controller interfaces that results in a change in DDR memory controller assignment
- Global placement of programmable logic that would influence NoC NMU/NSU
placementTip: In the IP integrator, you can constrain the location of the DDR memory controller to the appropriate site in the NoC View to reflect the assignment to perform during design placement. This improves the NoC QoS results correlation between IP integrator and a fully implemented design.
- The NOC compiler runs in the preplace mode, so the placement of fabric is driven by the placement of NoC instances that result in better NoC QoS.