Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs

ID 814346
Date 7/07/2025
Public

Visible to Intel only — GUID: hwh1678722638231

Ixiasoft

Document Table of Contents

12.2.5.2. IOBank Introduction

This section provides a brief overview of the IOBank block.

Note: In this chapter, “IOBank” is used as a generic term that refers to the block that contains the specific/dedicated IO pins and Hard Memory Controller required for SDRAM connected to the MPFE. In various other collaterals and tools, such as Quartus® Prime, Simics, U-Boot software, HPS register maps, and so on, the IOBank can also be called “IO96B” or “HPS Shared GPIO Bank” or “HPS Shared HSIO Bank”.
Note: For Agilex™ 5 E-Series and D-Series, IOBank_0 is IO Bank 3A and IOBank_1 is IO Bank 3B.
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.

The IOBank is the subsystem which houses the high-speed IO. It supports DDR, differential (LVDS + MIPI d-phy), and GPIO applications. Each I/O bank contains 96 general purpose I/Os and two high-efficiency hard memory controllers. The hard memory controllers support various memory types, each with different performance capabilities. You can bypass the hard memory controller and implement a soft memory controller in user logic.

Figure 295. IOBank Block Diagram