SK-AM62: Booting from eMMC in backup boot mode fails

Hi Gero,

The shared logs suggests you are using U-Boot from PSDK v8.6 however your edit says v9.2. Can you please clarify the exact version you are using and share the corresponding logs?

If it helps, I have verified the eMMC backup boot with PSDK v9.1

U-Boot SPL 2023.04-gafcd134e-dirty (Mar 29 2024 - 13:18:12 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Trying to boot from MMC1
spl: mmc boot mode: fs
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.9(release):v2.9.0-614-gd7a7135d32-dirty
NOTICE:  BL31: Built : 09:34:15, Aug 24 2023

U-Boot SPL 2023.04-gafcd134e-dirty (Mar 29 2024 - 13:18:21 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
SPL initial stack usage: 1856 bytes
MMC: no card present
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Trying to boot from MMC1
spl: mmc boot mode: fs
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed
am625_init: spl_boot_device: devstat = 0x1473 bootmedia = 0x9 bootindex = 1
Authentication passed


U-Boot 2023.04-gafcd134e-dirty (Mar 29 2024 - 13:18:21 +0530)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM rev A
DRAM:  2 GiB
Core:  72 devices, 32 uclasses, devicetree: separate
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
=> 

Regards,

Prashant

Hi Prashant,

Thank you for your help. I used sysfw 8.6.4 by accident, I rebuild everything with sysfw 9.2.7 but I still get the same error message:

U-Boot SPL 2023.04 (Apr 02 2024 - 14:24:17 +0200)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
mmc_load_image_raw_sector: mmc block read error
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image tispl.bin, err - -1
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Just to clarify, I'm not building with yocto, just the individual components themselves. Here's what I'm doing to follow along:

Setup:

# Clone all repos
git clone https://git.ti.com/git/ti-u-boot/ti-u-boot.git
git clone https://git.ti.com/git/processor-firmware/ti-linux-firmware.git
git clone https://git.ti.com/git/optee/ti-optee-os.git
git clone https://git.ti.com/git/atf/arm-trusted-firmware.git

# Checkout all repos to 09.02.00.009
for dir in *; do
    cd $dir
    git checkout 09.02.00.009
    cd ..
done

# Verify
for dir in *; do
    echo $dir:
    cd $dir
    git tag --points-at HEAD | grep ^[0-9]
    cd ..
done

Build:

# Setup build
export CC32=arm-linux-gnueabihf-
export CC64=aarch64-linux-gnu-
export LNX_FW_PATH=$PWD/ti-linux-firmware
export TFA_PATH=$PWD/arm-trusted-firmware
export OPTEE_PATH=$PWD/ti-optee-os

export UBOOT_CFG_CORTEXR=am62x_evm_r5_defconfig
export UBOOT_CFG_CORTEXA=am62x_evm_a53_defconfig
export TFA_BOARD=lite
unset TFA_EXTRA_ARGS
export OPTEE_PLATFORM=k3-am62x
export OPTEE_EXTRA_ARGS="CFG_WITH_SOFTWARE_PRNG=y"

# Build TF-A
cd arm-trusted-firmware
make CROSS_COMPILE=$CC64 ARCH=aarch64 PLAT=k3 SPD=opteed $TFA_EXTRA_ARGS TARGET_BOARD=$TFA_BOARD

# Build optee
cd ../ti-optee-os
make CROSS_COMPILE=$CC32 CROSS_COMPILE64=$CC64 CFG_ARM64_core=y $OPTEE_EXTRA_ARGS PLATFORM=$OPTEE_PLATFORM

# Build R5 SPL
cd ../ti-u-boot
make $UBOOT_CFG_CORTEXR
make CROSS_COMPILE=$CC32 BINMAN_INDIRS=$LNX_FW_PATH

# Build A53 SPL and U-Boot
make $UBOOT_CFG_CORTEXA
make CROSS_COMPILE=$CC64 BINMAN_INDIRS=$LNX_FW_PATH BL31=$TFA_PATH/build/k3/$TFA_BOARD/release/bl31.bin TEE=$OPTEE_PATH/out/arm-plat-k3/core/tee-raw.bin

Flash:

# I boot the board using sdcard into A53 u-boot, switches for SK E3:
# 01101000 11000010  (port=1, fs, primary=mmcsd, backup=mmcsd)
# then, in u-boot I flash the image onto the eMMC using DFU (I added DFU to u-boot on sd-card):
=> setenv dfu_alt_info 'uda part 0 1; tiboot3.bin fat 0 1; tispl.bin fat 0 1'
=> dfu 0 mmc 0

# Host:
dfu-util --alt tiboot3.bin --download tiboot3-am62x-gp-evm.bin
dfu-util --alt tispl.bin --download tispl.bin

# Switch off board, set switches to boot from emmc UDA (primary):
# 00101000 11000010  (port=0, fs, primary=mmcsd, backup=mmcsd)
# and test if the board comes up:
# It boots R5 SPL, loads tispl and starts ATF and OP-TEE then boots A53 SPL,
# there it hangs because there's no u-boot.img on the eMMC (expected).

# Switch off board, set switches to boot from emmc UDA (backup):
# 00101000 11010010  (port=0, fs, primary=eMMC, backup=mmcsd)
# I'm using eMMC mode as primary, but there's no image on hardware partition
# boot0, so backup boot will be used (I tested that boot0 is empty).
# Power on board and observe:

U-Boot SPL 2023.04 (Apr 02 2024 - 15:00:05 +0200)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
mmc_load_image_raw_sector: mmc block read error
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image tispl.bin, err - -1
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Oh, I think I just found the issue: If I use I2C as primary boot (nothing connected), then backup boot with MMCSD and port=0 (eMMC) works!

So the bug is: When using primary boot mode eMMC, then using backup boot mode MMCSD with port=0 (eMMC) does not work.

Any idea how to solve this? Or is this a hardware limitation? (Couldn't find it in the Errata.)

Hi Gero,

Gero Schwäricke said:

Oh, I think I just found the issue: If I use I2C as primary boot (nothing connected), then backup boot with MMCSD and port=0 (eMMC) works!

I was going to suggest the same. If you see in my working logs, the primary boot media is SPI and backup media is eMMC. I guess if I do the same boot switches configuration as yours, I would also see the issue.

Let me know dig through the code and see what's going on.

Regards,

Prashant

Hi Prashant,

Prashant Shivhare said:

Let me know dig through the code and see what's going on.

Sounds great, thank you! Let me know if I can support you in any way to figure this one out.

Best,
Gero

Prashant, you are a hero! This fixed the issue!

I would be great if this fix could be included upstream. Until then I will use this patch.

Thank you very much for the detailed explanation and the solution! Great TI support!