This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Following 3.1.1.6. OSPI/QSPI — Processor SDK AM62x Documentation for flashing U-boot Images to OSPI using TFTP server.
In Step 3 when we are trying to load tiboot3.bin I am getting the below result :
U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024
U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
U-Boot 2023.04 (Apr 26 2024 - 16:56:59 +0530)
SoC: AM62X SR1.0 HS-FS
Model: Texas Instruments AM62x LP SK
EEPROM not available at 80, trying to read at 81
Board: AM62-LP-SKEVM rev E2
DRAM: 2 GiB
Core: 81 devices, 33 uclasses, devicetree: separate
NAND: 0 MiB
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
=> setenv ipaddr 10.0.0.5
=>
=> setenv serverip 10.0.0.2
=> sf probe
=> tftp 0x060000000 tiboot3.bin
link up on port 1, speed 1000, full duplex
Using ethernet@8000000port@1 device
TFTP from server 10.0.0.2; our IP address is 10.0.0.5
Filename 'tiboot3.bin'.
TFTP error: trying to overwrite reserved memory...
=>
Can you please confirm which addresses should be given in the place of load address tftp ${loadaddr} tiboot3.bin for loading the image to OSPI?
Best Regards,
Vaibhav V Agavile
Hello Vaibhav,
Is loadaddr already preconfigured with an address? Please do "printenv loadaddr" to check this.
-Daolin