PROCESSOR-SDK-AM64X: Booting from eMMC

Jay Kaneria

Hi,

We have custom board based on AM6422B. I am trying to flash the emmc from the SD card linux. I have followed below steps from this reference.

echo 0 > /sys/block/mmcblk0boot0/force_ro

/* taken u-boot images from the SD card image */
mount -t fat /dev/mmcblk1

dd if=./tiboot3.bin of=/dev/mmcblk0boot0 seek=0
1176+1 records in
1176+1 records out

dd if=./tispl.bin of=/dev/mmcblk0boot0 seek=2048
1762+1 records in
1762+1 records out

dd if=./u-boot.img of=/dev/mmcblk0boot0 seek=6144
2049+0 records in
2048+0 records out

created the mmcblk0p1 partition from the mmcblk0 device and extraxted the rootfs in mmcblkp1 partition

/* Rebooted the board and stopped board at boot prompt and set mmc as below */

mmc partconf 0 1 1 1

mmc bootbus 0 2 0 0

Then changed boot switched to boot the board from emmc. So, I am getting below logs.

U-Boot SPL 2021.01 (Apr 10 2024 - 15:15:46 +0530)
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed 1
Using defaults for SBC
Resetting on cold boot to workaround ErrataID:i2331
resetting ...

U-Boot SPL 2021.01 (Apr 10 2024 - 15:15:46 +0530)
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed 1
Using defaults for SBC
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC1

U-boot is not going forward from this point. I tried the steps multiple time but the getting the same issue. Am I doing anything wrong here?

************************************************************************************************************************

Editing my query from here

************************************************************************************************************************

When i try to flash the u-boot, I am getting below error which I didn't noticed before.

# dd if=u-boot.img of=/dev/mmcblk0boot0 seek=6144
dd: error writing '/dev/mmcblk0boot0': No space left on device
2049+0 records in
2048+0 records out

Looks like mmcblk0boot0 is not big enough to hold the u-boot image and giving the space issue error. Is there way to resize the mmcblk0boot0 partition?

Regards,

Jay

over 1 year ago

0 Prashant Shivhare over 1 year ago

TI__Guru* 77701 points

Hi Jay,

Can you please try flashing the eMMC from U-Boot? Please refer the steps here:

https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-Memory.html#booting-tiboot3-bin-tispl-bin-and-u-boot-img-from-emmc-boot-partition-for-k3-class-of-socs

Regards,

Prashant

0 Jay Kaneria over 1 year ago in reply to Prashant Shivhare

Intellectual 590 points

Hi Prasant,

I have tried the steps you have suggested. But i faced same size issue.

=> mmc dev 0 1
switch to partitions #1, OK
mmc0(part 1) is current device
=> fatload mmc 1 ${loadaddr} tiboot3.bin
602247 bytes read in 27 ms (21.3 MiB/s)
=> mmc write ${loadaddr} 0x0 0x800

MMC write: dev # 0, block # 0, count 2048 ... 2048 blocks written: OK
=> fatload mmc 1 ${loadaddr} tispl.bin
902227 bytes read in 39 ms (22.1 MiB/s)
=> mmc write ${loadaddr} 0x800 0x1000

MMC write: dev # 0, block # 2048, count 4096 ... 4096 blocks written: OK
=> fatload mmc 1 ${loadaddr} u-boot.img
1172979 bytes read in 51 ms (21.9 MiB/s)
=> mmc write ${loadaddr} 0x1800 0x2000

MMC write: dev # 0, block # 6144, count 8192 ... MMC: block number 0x3800 exceeds max(0x2000)
0 blocks written: ERROR

I have tried the "mmc bootpart-resize" command as well. But that also not changing the size of "mmcblk0boot0" and "mmcblk0boot1" device. Is there any other way to change the size of boot0 and boot1 partition?

Regards,

Jay

0 Prashant Shivhare over 1 year ago in reply to Jay Kaneria

TI__Guru* 77701 points

Hi Jay,

It looks like you are using custom eMMC part which might not have large enough boot partition. Can you please share the output of "mmc info" command run from the U-Boot prompt to confirm the same?

Regards,

Prashant

0 Jay Kaneria over 1 year ago in reply to Prashant Shivhare

Intellectual 590 points

Hi Prasant,

Here is the "mmc info" command output.

=> mmc info
Device: mmc@fa10000
Manufacturer ID: 45
OEM: 100
Name: DG401
Bus Speed: 200000000
Mode: HS400 (200MHz)
Rd Block Len: 512
MMC version 5.1
High Capacity: Yes
Capacity: 14.7 GiB
Bus Width: 8-bit DDR
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 14.7 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

Regards,

Jay

0 Prashant Shivhare over 1 year ago in reply to Jay Kaneria

TI__Guru* 77701 points

Hi Jay,

Since your custom eMMC part has 4MB boot partitions, you will need to modify the default flash offsets of tispl.bin & u-boot.img to fit all three in 4MB. Please refer the following similar thread:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1305407/am623-usage-of-an-emmc-boot0-partition-of-4mb

Regards,

Prashant

Processors

Processors forum

PROCESSOR-SDK-AM64X: Booting from eMMC