Hard Processor System Technical Reference Manual: Agilex™ 3 SoCs

ID 848530
Date 6/23/2025
Public
Document Table of Contents

A.2.2.1. Feature Availability under SDM/HPS Ownership of Quad SPI Controller

The SDM or HPS cannot execute any feature or application that requires access to the QSPI device unless it has ownership of the QSPI controller.

This includes operations such as retrieving items from the QSPI, like the Linux file system, an encryption key, phase 2, partial reconfiguration FPGA image, and others. If the SDM has ownership of the QSPI controller, the HPS cannot access the QSPI device for reading or writing, and vice versa.

The following table describes the QSPI controller ownership requirement for different device functionalities.

Note: You need to select in the Quartus® Prime Pro Edition software the QSPI controller ownership (for SDM or HPS) based on the QSPI related features that your project requires to support.
Table 439.  QSPI Controller Ownership Requirement
Device

Feature/Application

(QSPI Ownership: HPS/SDM must own)

HPS loading from QSPI flash HPS loading Phase2 bitstream HPS loading Partial Reconfiguration bitstream RSU from HPS Attestation On Boarding BKPS
Agilex™ 3 HPS

HPS: If Phase2 bitstream is in QSPI flash.

SDM: If Phase2 bitstream is encrypted with AES key in QSPI flash. 69

HPS or SDM may own the QSPI controller under other scenarios following the above restrictions.

HPS: If PR bitstream is in QSPI flash.

SDM: If PR bitstream is encrypted with AES key in QSPI flash.69

HPS or SDM may own the QSPI controller under other scenarios following the above restrictions.

HPS SDM SDM SDM
69 When the Phase2 or PR bitstreams are encrypted, the SDM requires the AES key to decrypt these. If the AES key is in the QSPI flash, the SDM must own the QSPI controller so that it can access the key. In this case, Phase2 or PR bitstreams still need to be stored outside of the QSPI flash device so HPS can access them.