New Contributor
New ContributorHi Aik,
Yes, with some help I was able to determine the cause of the original error I was receiving when I tried to load u-boot using the Arm DS debugger:
+loadfile u-boot-socfpga/u-boot
Target Message: Memory access caused precise abort.
Debug Precise Abort Registers : DFSR = 0x00000805, DFAR = 0x01001020
ERROR(CMD16-TAD59-NAL18):
# in C:\Users\engineering\HD-MRPS\Linux_Boot\11-18-2023\debug-u-boot-A10.ds:27 while executing: loadfile u-boot-socfpga/u-boot
! Failed to load "u-boot"
! Download of 356,184 bytes to address S:0x01000040 failed while writing block of 4,096 bytes to address S:0x01000040
! Bus error on memory operation.ERROR(CMD656): The script C:\Users\engineering\HD-MRPS\Linux_Boot\11-18-2023\debug-u-boot-A10.ds failed to complete due to an error during execution of the script
We found that this error did not occur when following the debugger command line instructions instead of using the Arm DS debugger GUI:
cd a10_soc_devkit_ghrd/software/bootloader
~/intelFPGA_pro/23.3/nios2eds/nios2_command_shell.sh \
/opt/arm/developmentstudio-2021.1/bin/armdbg \
--cdb-entry="Intel SoC FPGA::Arria 10 SoC::Bare Metal Debug::Bare Metal Debug::Debug Cortex-A9_0::USB-Blaster" \
--cdb-entry-param="rvi_address=USB-BlasterII on localhost [3-3.1.1]:USB-BlasterII 3-3.1.1" \
--continue_on_error=true \
--stop_on_connect=false \
-s run-u-boot.ds
So, using the command line debugger instructions fixed the problem. I don't know why the loading of u-boot fails when using the Arm DS debugger GUI though even though it seems to be setup the same way and it calls the same script. Note that I did not use the nios2_command_shell, but I used the Intel SoC EDS Command Shell instead. It works just fine though. So, I can now successfully load u-boot using the command line debugger instructions.
Thanks,
Richard
