SK-AM62-LP: AM62x eMMC Boot Fails After Successful DFU Flash

gopal sharma

Part Number: SK-AM62-LP

Hi Team,

We are facing an issue after completing the steps mentioned in the support post below:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1582122/sk-am62-lp-rootfs-transfer-failure-via-dfu-file-size-exceeds-limit

U-Boot SPL 2025.01-gcd91d7360181-dirty (Oct 30 2025 - 14:52:37 +0530)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

The only difference between our procedure and the TI reference steps is that we are using the prebuilt tiboot3.bin from the SDK’s shared binaries.
We did not build tiboot3.bin ourselves because the build process reports an error during compilation.

cd ~/ti-processor-sdk-linux-am62xx-evm-11.00.09.04/board-support/optee-os-4.5.0+git/

$ make CROSS_COMPILE="$CROSS_COMPILE_32" CROSS_COMPILE64="$CROSS_COMPILE_64" PLATFORM=k3-am62x-lp CFG_ARM64_core=y
Example of Command:-

Error:-

Below is an example command to build tispl.bin and u-boot.img, which will be saved in $UBOOT_DIR/out/a53:

cd $UBOOT_DIR
make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" CC="$CC_64" \
BL31=$TFA_DIR/build/k3/lite/release/bl31.bin \
TEE=$TI_LINUX_FW_DIR/bl32.bin \
O=$UBOOT_DIR/out/a53 \
BINMAN_INDIRS=$TI_LINUX_FW_DIR -j12

Below are a few logs collected during our U-Boot testing for your reference.

=> mmc dev 0 1
switch to partitions #1, OK
mmc0(part 1) is current device
=> mmc read ${loadaddr} 0x0 0x10
MMC read: dev # 0, block # 0, count 16 ... 16 blocks read: OK
=> md ${loadaddr}
82000000: 58088230 40068230 010203a0 36140202  0..X0..@.......6
82000010: 9160ae05 29513578 55903fec d9ff1351  ..`.x5Q).?.UQ...
82000020: 307f5a34 2a09060d f7864886 0d01010d  4Z.0...*.H......
82000030: 81300005 300b319d 55030609 02130604  ..0..1.0...U....
82000040: 0b315355 03060930 0c080455 31585402  US1.0...U....TX1
82000050: 060d300f 07045503 6144060c 73616c6c  .0...U....Dallas
82000060: 25302731 04550306 541e0c0a 73617865  1'0%..U....Texas
82000070: 736e4920 6d757274 73746e65 636e4920   Instruments Inc
82000080: 6f70726f 65746172 30133164 55030611  orporated1.0...U
82000090: 0a0c0b04 636f7250 6f737365 13317372  ....Processors1.
820000a0: 03061130 0c030455 2049540a 70707553  0...U....TI Supp
820000b0: 3174726f 061b301d 48862a09 010df786  ort1.0...*.H....
820000c0: 0e160109 70707573 4074726f 632e6974  ....support@ti.c
820000d0: 1e306d6f 35320d17 30333031 33323930  om0...2510300923
820000e0: 175a3632 3135320d 30393231 32333239  26Z..25112909232
820000f0: 81305a36 300b319d 55030609 02130604  6Z0..1.0...U....
=> mmc dev 0 1
switch to partitions #1, OK
mmc0(part 1) is current device
=> mmc read ${loadaddr} 0x0 0x20
MMC read: dev # 0, block # 0, count 32 ... 32 blocks read: OK
=> md ${loadaddr} 0x40
82000000: 58088230 40068230 010203a0 36140202  0..X0..@.......6
82000010: 9160ae05 29513578 55903fec d9ff1351  ..`.x5Q).?.UQ...
82000020: 307f5a34 2a09060d f7864886 0d01010d  4Z.0...*.H......
82000030: 81300005 300b319d 55030609 02130604  ..0..1.0...U....
82000040: 0b315355 03060930 0c080455 31585402  US1.0...U....TX1
82000050: 060d300f 07045503 6144060c 73616c6c  .0...U....Dallas
82000060: 25302731 04550306 541e0c0a 73617865  1'0%..U....Texas
82000070: 736e4920 6d757274 73746e65 636e4920   Instruments Inc
82000080: 6f70726f 65746172 30133164 55030611  orporated1.0...U
82000090: 0a0c0b04 636f7250 6f737365 13317372  ....Processors1.
820000a0: 03061130 0c030455 2049540a 70707553  0...U....TI Supp
820000b0: 3174726f 061b301d 48862a09 010df786  ort1.0...*.H....
820000c0: 0e160109 70707573 4074726f 632e6974  ....support@ti.c
820000d0: 1e306d6f 35320d17 30333031 33323930  om0...2510300923
820000e0: 175a3632 3135320d 30393231 32333239  26Z..25112909232
820000f0: 81305a36 300b319d 55030609 02130604  6Z0..1.0...U....
=> mmc read ${loadaddr} 0x400 0x20
MMC read: dev # 0, block # 1024, count 32 ... 32 blocks read: OK
=> md ${loadaddr} 0x40
82000000: edfe0dd0 2f0d1200 38000000 dc081200  ......./...8....
82000010: 28000000 11000000 02000000 00000000  ...(............
82000020: 6d000000 a4081200 00000000 00000000  ...m............
82000030: 00000000 00000000 01000000 00000000  ................
82000040: 03000000 04000000 63000000 02300369  ...........ci.0.
82000050: 03000000 04000000 54000000 01000000  ...........T....
82000060: 03000000 22000000 48000000 666e6f43  ......."...HConf
82000070: 72756769 6f697461 6f74206e 616f6c20  iguration to loa
82000080: 54412064 6e612046 50532064 0000004c  d ATF and SPL...
82000090: 01000000 67616d69 00007365 01000000  ....images......
820000a0: 00667461 03000000 04000000 42000000  atf............B
820000b0: 00000080 03000000 04000000 3d000000  ...............=
820000c0: 00000080 03000000 15000000 3a000000  ...............:
820000d0: 2d6d7261 73757274 2d646574 6d726966  arm-trusted-firm
820000e0: 65726177 00000000 03000000 05000000  ware............
820000f0: 2e000000 656e6f6e 00000000 03000000  ....none........
=> mmc read ${loadaddr} 0x1400 0x20
MMC read: dev # 0, block # 5120, count 32 ... 32 blocks read: OK
=> md ${loadaddr} 0x40
82000000: edfe0dd0 93f41400 38000000 70f01400  ...........8...p
82000010: 28000000 11000000 02000000 00000000  ...(............
82000020: 63000000 38f01400 00000000 00000000  ...c...8........
82000030: 00000000 00000000 01000000 00000000  ................
82000040: 03000000 04000000 53000000 03300369  ...........Si.0.
82000050: 03000000 27000000 47000000 20544946  .......'...GFIT 
82000060: 67616d69 69772065 6d206874 69746c75  image with multi
82000070: 20656c70 666e6f63 72756769 6f697461  ple configuratio
82000080: 0000736e 01000000 67616d69 00007365  ns......images..
82000090: 01000000 6f6f6275 00000074 03000000  ....uboot.......
820000a0: 04000000 42000000 00008080 03000000  .......B........
820000b0: 05000000 36000000 656e6f6e 00000000  .......6none....
820000c0: 03000000 04000000 31000000 006d7261  ...........1arm.
820000d0: 03000000 07000000 2e000000 6f622d75  ............u-bo
820000e0: 0000746f 03000000 09000000 29000000  ot.............)
820000f0: 6d726966 65726177 00000000 03000000  firmware........
=> mmc partconf 0 1 1 1
=> mmc bootbus 0 2 0 0
Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x0
=> mmc partconf 0
EXT_CSD[179], PARTITION_CONFIG:
BOOT_ACK: 0x1
BOOT_PARTITION_ENABLE: 0x1 (boot0)
PARTITION_ACCESS: 0x1 (boot0)

Also, if we try to flash again and follow the process from the beginning (using am62x_r5_usbdfu.config), then after running
sudo dfu-util -R -a u-boot.img -D u-boot.img
(with the USB peripheral host boot switches set), the board boots successfully.
However, after switching the boot mode to eMMC, it shows the following message on the console:

U-Boot SPL 2025.01-gcd91d7360181-dirty (Oct 30 2025 - 14:52:37 +0530)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Could you please help us understand if using the prebuilt tiboot3.bin could cause this issue, or if there are any additional steps required to ensure eMMC boot works correctly?

Regards,
Gopal Sharma

14 days ago

0 Meet Thakar 13 days ago

TI__Genius 14175 points

Hi Gopal,

Please refer to this FAQ: [FAQ] SK-AM62: How to flash eMMC using USB DFU on AM62x-SK E2

You have to keep 2 sets of boot images, one for DFU booting (this is done by using am62x_evm_r5_usbdfu_defconfig) and then another one for flashing and eMMC boot, if you use the binaries built with DFU configuration for EMMC boot then it will not work, you can use the prebuilt images for this.