AN 709: HPS SoC Boot Guide - Cyclone V SoC Development Kit

Download PDF
ID 683265
Date 1/27/2016
Public
Document Table of Contents
Document Table of Contents x
1. AN 709: HPS SoC Boot Guide - Cyclone V SoC Development Kit
1. AN 709: HPS SoC Boot Guide - Cyclone V SoC Development Kit x
1.1. Introduction 1.2. Boot Overview 1.3. Boot Duration 1.4. Boot Debugging 1.5. Boot Examples 1.6. Document Revision History
1.1. Introduction x
1.1.1. Prerequisite
1.2. Boot Overview x
1.2.1. Boot Flow 1.2.2. Boot Sources 1.2.3. Boot Clocks
1.2.1. Boot Flow x
1.2.1.1. Boot ROM 1.2.1.2. Preloader 1.2.1.3. Bootloader
1.2.2. Boot Sources x
1.2.2.1. Boot from SD/MMC 1.2.2.2. Boot from QSPI 1.2.2.3. Boot from NAND 1.2.2.4. Boot from FPGA 1.2.2.5. FPGA Fallback Boot 1.2.2.6. Boot from RAM on Warm Reset
1.3. Boot Duration x
1.3.1. Optimizing Boot Duration 1.3.2. Boot Duration Measurements
1.3.1. Optimizing Boot Duration x
1.3.1.1. Hardware Powerup Sequence 1.3.1.2. Boot ROM 1.3.1.3. Preloader 1.3.1.4. Bootloader 1.3.1.5. Linux Kernel 1.3.1.6. Init Scripts
1.4. Boot Debugging x
1.4.1. Boot ROM 1.4.2. Preloader 1.4.3. U-Boot
1.4.2. Preloader x
1.4.2.1. Debugging the Preloader from ARM DS-5 AE
1.5. Boot Examples x
1.5.1. Bare-Metal Application 1.5.2. Booting from SD/MMC – Custom Partition 1.5.3. Booting from SD/MMC – FAT Partition 1.5.4. Booting from QSPI Flash 1.5.5. Booting from FPGA
1.5.5. Booting from FPGA x
1.5.5.1. Overview 1.5.5.2. Hardware Design 1.5.5.3. Building and Running the Example
1. AN 709: HPS SoC Boot Guide - Cyclone V SoC Development Kit

1.5.4. Booting from QSPI Flash

This example demonstrates how to boot from the QSPI Flash. Both the Preloader and the Bare-metal application are stored in QSPI Flash.

The steps required to run this scenario are:

  1. Build the sample bare-metal application or simply use the provided file hello-mkimage.bin directly.
  2. Generate a Preloader based on the GHRD provided with SoC EDS. Make sure to select the following options:
    • Check the option spl.boot.BOOT_FROM_QSPI
    • Uncheck the other boot options (spl.boot.BOOT_FROM_RAM, spl.boot.BOOT_FROM_SDMMC, spl.boot.BOOT_FROM_NAND)
      Note: spl.boot.QSPI_NEXT_BOOT_IMAGE = 0x60000. This is the location where the bare-metal application image needs to be stored.
    • Check the option spl.boot.SDRAM_SCRUBBING and spl.boot.SDRAM_SCRUB_REMAIN_REGION. This zeroes out the SDRAM, preventing any ECC errors to occur during bare-metal program execution.
    • Uncheck the option spl.boot.WATCHDOG_ENABLE. This is because we are not kicking the watchdog in our bare-metal application.
  3. Compile the Preloader. This creates the file preloader-mkpimage.bin.
  4. Set the board to boot from SD card by configuring the BOOTSEL jumpers like this:
    • BOOTSEL0 (J28): left
    • BOOTSEL1 (J29): left
    • BOOTSEL2 (J30): left
  5. Connect the USB Blaster USB cable from board to the host PC. This is needed by the HPS Flash Programmer used in the next step.
  6. Write the Preloader and the application images to the QSPI Flash by starting an Embedded Command Shell and then running the following commands:
    • quartus_hps -c 1 -o PV preloader-mkpimage.bin
    • quartus_hps -c 1 -o PV -a 0x60000 hello-mkimage.bin
  7. Power-cycle the board or reset the HPS by pressing the COLD reset button (S7).
    The board boots, Preloader messages are displayed, then “Hello World” is displayed by the bare-metal application.
    Figure 11. Booting from QSPI Flash
Related Information
Level Two Title