Tool/software:
Hello,
I want to do eMMC boot on a custom board equipped with AM6411, but after power on, the following log is displayed and the boot process is stopped.
***************************************************************
U-Boot SPL 2023.04-dirty (Jan 23 2025 - 16:04:31 +0900)
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -19
Resetting on cold boot to workaround ErrataID:i2331
Please resend tiboot3.bin in case of UART/DFU boot
resetting ...
***************************************************************
The eMMC used is IS21ES08GA.
When you run the mmcinfo command with SD boot, the following response is displayed:
***************************************************************
=> mmcinfo
Device: mmc@fa10000
Manufacturer ID: 9d
OEM: 1
Name: IS008G
Bus Speed: 200000000
Mode: HS200 (200MHz)
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
***************************************************************
The difference in partitions compared to EVM has been addressed.
I am using the following command to write it:
***************************************************************
mmc dev 0 1
fatload mmc 1 0x90000000 tiboot3.bin
mmc write 0x90000000 0x0 0x800
fatload mmc 1 0x90000000 tispl.bin
mmc write 0x90000000 0x800 0x800
fatload mmc 1 0x90000000 u-boot.img
mmc write 0x90000000 0x1000 0xe00
***************************************************************
When I set backup boot (SD), SD boot will be performed, so I can confirm that tiboot3.bin is running.
When I reset the device(resetting ...), I could see that the CMD pin connecting the eMMC was working, but the data pin was not.
I am using ti-u-boot-2023.04+gitAUTOINC+8366064208. Is it possible to control the behavior at reset with this?
Could you please tell me what to do?
By the way, in eMMC (UDA) mode, I was able to reload tiboot3.bin and execute the u-boot command.
I am using the following command:
***************************************************************
mmc dev 0 0
fatload mmc 1 0x90000000 tiboot3.bin
mmc write 0x90000000 0x0 0x800
fatload mmc 1 0x90000000 tispl.bin
mmc write 0x90000000 0x800 0x800
fatload mmc 1 0x90000000 u-boot.img
mmc write 0x90000000 0x1000 0xe00
mmc partconf 0 1 0 0
***************************************************************
In this mode, even if I create mmcblk0p1 from /dev/mmcblk0 and expand a file system into it, it will not boot properly.
Furthermore, if I write u-boot related files with the above mmc write command, mmcblk0p1 disappears.
Is there something wrong with the procedure or settings?
If booting Linux is successful with eMMC, it doesn't matter whether using eMMC mode or eMMC(UDA) mode.
I would appreciate some advice from someone who thinks it might be an easy solution.
Regards,
Kato.
