Hard Processor System Component Reference Manual: Agilex™ 5 SoCs
ID
813752
Date
4/10/2025
Public
A newer version of this document is available. Customers should click here to go to the newest version.
1. Introduction to the Agilex™ 5 Hard Processor System Component
2. Configuring the Agilex™ 5 Hard Processor System Component
3. Simulating the Agilex™ 5 HPS Component
4. Simulating the Agilex™ 5 HPS bridges (H2F, LWH2F, and F2SDRAM)
5. Design Guidelines
6. Document Revision History for the Hard Processor System Component Reference Manual Agilex™ 5 SoCs
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)
2.3.1. Configurations for HPS IP
2.3.2. Configurations for HPS EMIF IP
2.3.3. Graphical Connections of HPS to HPS-EMIF
2.3.4. Configuration when using ECC
2.3.5. Configuration of HPS EMIF Calibration Settings
2.3.6. Supported Memory Protocols Among Device Families
2.3.7. IO96 Bank and Lane Usage for HPS EMIF
2.3.8. Quartus Report of I/O Bank Usage
2.3.9. Debugging with the External Memory Interface Debug Toolkit
2.2.2.1. FPGA to HPS Subordinate
FPGA-to-HPS subordinate interface allow the FPGA manager to issue transactions to the HPS.
- FPGA-to-HPS subordinate interface type is default to ACE5-Lite. You must use the ACE5-Lite Cache Coherency Translator (CCT) FPGA IP to connect any AXI Manager in the fabric to the F2H bridge.
Figure 7. Cache Coherency Translator (CCT) Use Case
- Enable/Data Width drop-down to configure this manager interface's data widths
- Unused
- 256-bit
- Interface Address Width is configurable from 40 bits down to 20 bits, which allows the FPGA fabric to access the majority of the HPS address space. To facilitate initiators in the FPGA logic with a smaller address width than the bridge in accessing the HPS address space, you can use the Intel Address Span Extender component.
- Enable System MMU option enables the SMMU (TBU) feature on the FPGA-to-HPS path. This feature supports virtual addressing of the DDR/HPS. The SMMU ports are enabled and exposed as extended ARUSER and AWUSER port at top-level.
- Enable System MMU Ports option enables the SMMU (TBU) ports on the FPGA-to-HPS path. This feature exposes the two fpga2hps ports, SECSID and SID port at top-level.
When this bridge is enabled, the interfaces: fpga2hps, fpga2hps_clock, and fpga2hps_reset are made available.
Note: All interfaces must be properly connected to/from the HPS IP block to another appropriate IP block within the system or exported. Failure to complete this task may result in errors during the Quartus Compilation process.
Note: The h2f_reset signal must be connected to the fpga2hps_reset signal for proper bridge operation.
Note: Pins that are not used directly by the HPS-EMIF are available for I/O sharing with other protocols, such as GPIO, MIPI, LVDS SERDES, or PHY Lite, with certain HPS bridge restrictions. These restrictions are described in the tables in the Agilex™ 5 EMIF IP for Hard Processor Subsystem (HPS) section of the External Memory Interfaces (EMIF) IP User Guide: Agilex™ 5 FPGAs and SoCs.
Related Information