Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs

ID 814346
Date 11/27/2024
Public
Document Table of Contents

8.7.5.2. HPS Boot First

If the HPS Boot First Mode has been selected, and after a POR, then the SDM drives the HPS_COLD_nRESET signal to output low. At this point, referring to the Device Configuration User Guide: Agilex™ 5 FPGAs and SoCs , the bitstream configuration file containing the FSBL must be resent to the SDM using the same interface that the MSEL[2:0] pins specified during POR. After the bitstream has been received, the SDM releases the HPS from reset, and the HPS_COLD_nRESET signal is configured as an input and can be pulled high by the external pull-up resister.

For HPS first configuration, the HPS application controls the time between CONF_DONE and INIT_DONE. The INIT_DONE signal does not assert until after the software running on the HPS such as U-Boot or the operating system (OS) initiates the configuration, the FPGA configures, and enters user mode. The following figures show the HPS boot first behavior.

Figure 280.  HPS_COLD_nRESET Signal Behavior (HPS First, POR assert)

If the HPS Boot First Mode has been selected, and after nCONFIG has been asserted, then the SDM drives the HPS_COLD_nRESET signal to output low. After the bitstream has been received, the SDM releases the HPS from reset, and the HPS_COLD_nRESET signal is configured as an input and can be pulled high by the external pull-up resister.

For HPS first configuration, the HPS application controls the time between CONF_DONE and INIT_DONE. The INIT_DONE signal does not assert until after the software running on the HPS such as U-Boot or the operating system (OS) initiates the configuration, the FPGA configures, and enters user mode.

Figure 281. HPS_COLD_nRESET Signal Behavior (HPS First, nCONFIG assert)