Visible to Intel only — GUID: ioh1677199040346
Ixiasoft
1. Answers to Top FAQs
2. Network-on-Chip (NoC) Overview
3. Hard Memory NoC in Intel Agilex® 7 M-Series FPGAs
4. NoC Design Flow in Intel® Quartus® Prime Pro Edition
5. NoC Real-time Performance Monitoring
6. Simulating NoC Designs
7. NoC Power Estimation
8. Hard Memory NoC IP Reference
9. Document Revision History of Intel Agilex® 7 M-Series FPGA Network-on-Chip (NoC) User Guide
4.4.1. General NoC IP Connectivity Guidelines
4.4.2. Connectivity Guidelines: NoC Initiators for Fabric AXI4 Managers
4.4.3. Connectivity Guidelines: NoC Targets for Fabric AXI4 Managers
4.4.4. Connectivity Guidelines: NoC Clock Control
4.4.5. Connectivity Guidelines: NoC Initiators for HPS
4.4.6. Connectivity Guidelines: NoC Targets for HPS
6.1. Adding NoC Connectivity and Address Mapping to the Simulation Netlist
6.2. Generating a Simulation Registration Include File (NoC Assignment Editor Connection Flow)
6.3. Generating a Simulation Registration Include File (Platform Designer Connection Flow)
6.4. Contents of Simulation Registration Include File
8.1.2.1. NoC Initiator Intel FPGA IP AXI4/AXI4 Lite Interfaces
8.1.2.2. NoC Initiator AXI4 User Interface Signals
8.1.2.3. NoC Initiator Intel FPGA IP AXI4 Lite User Interface Signals
8.1.2.4. NoC Initiator Intel FPGA IP Clock and Reset Signals
8.1.2.5. NoC Initiator Intel FPGA IP Platform Designer-Only Signals
Visible to Intel only — GUID: ioh1677199040346
Ixiasoft
4.6.1. Using Interface Planner
The following steps describe basic operation of the Interface Planner to place NoC design elements:
- Ensure that you have already run Analysis & Synthesis, as this document previously describes.
- To open the Interface Planner click Tools > Interface Planner,
- On the Flow control, click Initialize Interface Planner.
- On the Flow control, click View Assignments.
- On the Assignments tab, enable or disable specific or groups of project assignments to resolve any conflicts or experiment with different settings. You can filter the list of assignments by assignment name or status.
- Click Update Plan on the Flow control to apply the enabled project assignments to your interface plan.
- Click Plan Design on the Flow control to interactively place IP cores and other design elements in legal locations in the device periphery. All placeable elements, including NoC elements and periphery elements, appear in the Design Elements list. Refer to Recommended Placement Order for NoC Elements in Interface Planner.
- Use any of the following methods to place design elements in the Chip View:
- Drag NoC elements from the Design Elements list and drop them onto available device resources in the Chip view. You may experience a small delay while dragging as Interface Planner calculates the legal locations.
- To allow Interface Planner to place an unplaced design element in a legal location, right-click and select Autoplace Selected. You must use Autoplace Selected for all unplaced clocks.
- Right-click an element in the Design Elements list, and then click Generate Legal Locations to display a list of Legal Locations for the element. Click any legal location in the list to highlight the location in the floorplan. Double-click any location in the list to place the element in the location.
- After making all necessary location assignments in Interface Planner, validate the placement by clicking Validate Plan in the Flow pane.
- To generate a Tcl script to apply the placement constraints to your project, click Export Constraints in the Flow pane. To automatically run the Tcl script, enable Apply Assignments.
Figure 28. Export Physical Constraints from Interface Planner to Your Project
- To report whether the NoC initiator and target location placement allows your design to meet the bandwidth and transaction size requirements, click the Reports tab, and then double-click Report NoC Performance in the Tasks pane. For report details, refer to NoC Performance Reports in Interface Planner.
Note: Lower-speed memory protocols and other I/O functions that you implement in the GPIO-B blocks, and that bypass the NoC, can cause conflicts that prevent the use of certain initiator locations. Therefore, before assigning any initiator locations, place HBM2e and external memory controllers, as well as any fixed-location lower speed protocols or GPIO.
For more details on placing NoC initiators and targets, refer to the following related topics: