1.1. Boot Process 1.2. Boot Stages 1.3. Boot Devices 1.4. Second-Stage Boot Loader Support Package Generator Tool 1.5. Generating a Boot Loader with an External Flash Boot Device 1.6. Boot and FPGA Configuration 1.7. Boot Debugging 1.8. Appendix A: Building the UEFI Boot Loader 1.9. Revision History for Arria 10 SoC Boot User Guide
1.7.4. Boot Flash Device Issues
If the HPS is executing software, but the boot ROM fails to load the boot loader image, possible causes could be that:
- The boot loader images are corrupted in the boot device flash.
- The boot loader images are valid but the boot flash device communication has errors.
- The boot loader image loads successfully, but runtime execution fails due to a software bug.
To help reduce flash device communication issues, set CSEL=0x0. This prevents the boot ROM from reprogramming the PLLs and forces the boot ROM to use the lowest communication speed with the device.
Flash memory signals should be monitored, if available, with proper test and measurement equipment (logic analyzer or oscilloscope) to:
- Determine if the duration of the communication is not within specification
- Observe if the boot ROM communication is prematurely aborted
- Verify signal integrity, such as voltage levels and rise and fall times
- Capture (with a logic analyzer) HPS and flash device communication
If problems still persist and a debugger connection is available, then the contents of the upper 4KB of on-chip RAM can be dumped from the debugger for Intel® to analyze.
Did you find the information on this page useful?