Visible to Intel only — GUID: kdx1686332917228
Ixiasoft
2.1. Parameterizing the HPS Component
2.2. HPS-FPGA Interfaces
2.3. SDRAM
2.4. HPS Clocks, Reset, Power
2.5. I/O Delays
2.6. Pin Mux and Peripherals
2.7. Generating and Compiling the HPS Component
2.8. Using the Address Span Extender Component
2.9. Configuring the Agilex™ 5 Hard Processor System Component Revision History
2.2.1.1. Enable MPU Standby and Event Signals
2.2.1.2. Enable General Purpose Signals
2.2.1.3. Enable Debug APB* Interface
2.2.1.4. Enable System Trace Macrocell (STM) Hardware Events
2.2.1.5. Enable SWJ-DP JTAG Interface
2.2.1.6. Enable FPGA Cross Trigger Interface
2.2.1.7. Enable AMBA* Trace Bus (ATB)
3.1. Simulation Flows
3.2. Running the Simulation of the Design Examples
3.3. Clock and Reset Interface
3.4. FPGA-to-HPS AXI* Subordinate Interface
3.5. FPGA-to-SDRAM AXI* Subordinate Interface
3.6. HPS-to-FPGA AXI* Initiator Interface
3.7. Lightweight HPS-to-FPGA AXI* Initiator Interface
3.8. Simulating the Agilex™ 5 HPS Component Revision History
Visible to Intel only — GUID: kdx1686332917228
Ixiasoft
2.2.3. DMA Controller Interface
The DMA controller interface allows soft IP in the FPGA fabric to communicate with the DMA controller in the HPS. You can configure up to eight separate interface channels by clicking on the dropdown in the Enabled column for the corresponding channel row. Each DMA peripheral request interface conduit f2h_dma<n> contains the following three signals, where <n> corresponds to a specific request interface enabled in Platform Designer:
- f2h_dma<n>_req—This signal is used to request burst transfer using the DMA.
- f2h_dma<n>_single—This signal is used to request single word transfer using the DMA.
- f2h_dma<n>_ack—This signal indicates the DMA acknowledgment upon requests from the FPGA.
Figure 8. Platform Designer DMA Peripheral Request Sub-window