Visible to Intel only — GUID: qfi1688590768195
Ixiasoft
1. Introduction
2. FPGA Configuration First Mode
3. HPS Boot First Mode
4. Creating the Configuration Files
5. HPS Boot Flows
6. Configuring the FPGA Fabric from HPS Software
7. Debugging the Agilex™ 5 SoC FPGA Boot Flow
8. Document Revision History for the Hard Processor System Booting User Guide: Agilex™ 5 SoCs
4.1. Overview
4.2. Quartus® Prime Hardware Project Compilation
4.3. Bootloader Software Compilation
4.4. Programming File Generator
4.5. Configuration over JTAG
4.6. Configuration from QSPI
4.7. Configuration over AVST
4.8. Configuration via Protocol
4.9. Remote System Update
4.10. Partial Reconfiguration
4.11. Preserving SDRAM Content across HPS Resets for Agilex™ 5 Devices
Visible to Intel only — GUID: qfi1688590768195
Ixiasoft
5.1. U-Boot ATF Linux* Boot
The following figure shows the overview of the HPS Boot Flow using a U-Boot as HPS Bootloader to boot to the Linux* OS.
Figure 37. The U-Boot ATF Linux* Boot Flow
The boot flow is described in steps below:
- The Configuration Management Firmware (CMF), which is a part of the signed configuration bitstream, running on the SDM loads the FSBL, which is U-Boot SPL, into HPS On-Chip RAM and then bring the HPS boot core out from reset.
- The U-Boot SPL loads the SSBL, which is ATF BL31 and U-Boot proper (SSBL), into DDR.
- The U-Boot SPL jumps to the ATF BL31.
- The ATF BL31 sets up the GIC, EL3 environment, and initializes the PSCI services. PSCI services in ATF remain active or available once ATF jumps to U-Boot.
- The ATF BL31 jumps to the U-Boot proper.
- The U-Boot proper loads the Linux* OS into the DDR.
- The U-Boot jumps to the Linux* OS.
Note: The U-Boot proper and the Linux* OS can access the SDM FPGA features through ATF BL31 through the Arm* Secure Monitor Call (SMC).
For information on Exception Levels, refer to Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs.
Related Information