SK-AM62X-BOOT ISSUE

Pavithra P

Part Number: SK-AM62
Other Parts Discussed in Thread: AM625

Tool/software:

Hi everyone,

1)I have used my build image & successfully flash the SD Card for AM62X board.

2) I am used SDK version like 09_01_00_08 on Linux.Now i was changed the boot switch on sd card mode after board is fully not booting?why this issue is came.please resolve my issue?i was attached the logs below.

U-Boot SPL 2021.01-g74fc69c889 (Mar 15 2024 - 05:34:49 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
Trying to boot from MMC2

U-Boot 2021.01-g74fc69c889 (Mar 15 2024 - 05:34:49 +0000)

SoC: AM62X SR1.0
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-SKEVM rev E3
DRAM: 2 GiB
MMC: mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Net: eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
gpt_verify_headers: *** ERROR: Invalid GPT ***
Verify GPT: error!
Broken MMC partition scheme
Running Fastboot...

over 2 years ago

0 Bin Liu over 2 years ago

TI__Guru**** 180866 points

Hi,

I am routing your query to our U-Boot MMC expert for comments.

0 Prashant Shivhare over 2 years ago in reply to Bin Liu

TI__Guru* 86011 points

Hello,

Can you please run the following commands from U-Boot prompt and share the logs

=> printenv mmcdev
=> printenv bootpart
=> mmc dev 0
=> mmc part
=> mmc dev 1
=> mmc part
=> run args_mmc
=> printenv bootargs

Regards,

Prashant

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

Hello,

Thankyou for your information. I attached the logs below,

1)=> printenv mmcdev
mmcdev=0
2)=> printenv bootpart
bootpart=0:2
3)=> mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
4)=> mmc part

Partition Map for MMC device 0 --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
1     2048            271644          28016719-01     0c Boot
2     274432          1166520         28016719-02     83
5)=> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
6)=> mmc part

Partition Map for MMC device 1 --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
1     2048            271644          28016719-01     0c Boot
2     274432          1166520         28016719-02     83
7)=> run args_mmc
8)=> printenv bootargs
bootargs=console=ttyS2,115200n8 root=PARTUUID=28016719-02 rw rootfstype=ext4 rootwait
=>

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Pavithra P said:
1)=> printenv mmcdev
mmcdev=0
2)=> printenv bootpart
bootpart=0:2

May I know why you have changed the mmcdev and bootpart values from their default ones

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

hello,

Now, you mentioned above that default one i was set. after also not booting again same issue is came?

u-boot log i attached below.

=> printenv mmcdev
mmcdev=1
=> printenv bootpart
bootpart=1:2
=> run args_mmc
=> printenv bootargs
bootargs=console=ttyS2,115200n8 root=PARTUUID=28016719-02 rw rootfstype=ext4 rootwait
=>

U-Boot log

=============

U-Boot SPL 2021.01-g74fc69c889 (Mar 15 2024 - 05:38:34 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE: BL31: v2.6(release):08.04.00.002-dirty
NOTICE: BL31: Built : 05:29:11, Mar 15 2024

U-Boot SPL 2021.01-g74fc69c889 (Mar 15 2024 - 05:34:49 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
Trying to boot from MMC2

U-Boot 2021.01-g74fc69c889 (Mar 15 2024 - 05:34:49 +0000)

SoC:   AM62X SR1.0
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-SKEVM rev E3
DRAM: 2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
gpt_verify_headers: *** ERROR: Invalid GPT ***
Verify GPT: error!
Broken MMC partition scheme
Running Fastboot...

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Hello,

Can you please share the output of the following command

=> env print

The output will be long so please use "Insert -> Code" option to attach them in a Code Block. This helps keep the reply short and more readable.

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

Hello,

I attached logs below

=> env print
addr_fit=0x90000000
android_boot=1
arch=arm
args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000 ${mtdpar}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUU}
args_usb=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUU}
avb_verify=avb init ${mmcdev}; avb verify $slot_suffix;
baudrate=115200
board=am62x
board_name=am62x_skevm
board_rev=E3
board_serial=0174
board_software_revision=01
boot=mmc
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${pref}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} ei
boot_efi_bootmgr=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};i
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr}}
boot_fdt=try
boot_fit=0
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=linux fastboot recovery system panic
bootargs=console=ttyS2,115200n8 root=PARTUUID=<your-partition-uuid> rw rootfstyt
bootcmd=run distro_bootcmd
bootcmd_fastboot=if test "${android_boot}" -eq 1; then;setenv run_fastboot 0;ifi
bootcmd_linux=if test "${android_boot}" -eq 0; then;run findfdt; run envboot; ri
bootcmd_panic=if test "${android_boot}" -eq 1; then;fastboot 0; reset;fi
bootcmd_recovery=if test "${android_boot}" -eq 1; then;setenv run_recovery 0;ifi
bootcmd_system=if test "${android_boot}" -eq 1; then;echo Loading Android boot i
bootdelay=2
bootdir=/boot
bootenvfile=uEnv.txt
bootm_size=0x10000000
bootpart=1:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyS2,115200n8
cpu=armv8
default_device_tree=k3-am625-sk.dtb
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;ti1
dfu_alt_info_mmc=boot part 1 1;rootfs part 1 2;tiboot3.bin fat 1 1;tispl.bin fa1
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000;tispl.bin raw 0x080000 0x200000;0
dfu_alt_info_ram=tispl.bin ram 0x80080000 0x200000;u-boot.img ram 0x81000000 0x0
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
dtboaddr=0x89000000
efi_dtb_prefixes=/ /dtb/ /dtb/current/
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mm;
eth1addr=70:ff:76:1e:a4:a5
ethaddr=f4:84:4c:fc:21:a5
fdt_addr_r=0x88000000
fdtaddr=0x88000000
fdtcontroladdr=f7eeb000
fdtoverlay_addr_r=0x80200000
findfdt=setenv name_fdt ${default_device_tree};setenv fdtfile ${name_fdt}
finduuid=part uuid ${boot} ${bootpart} uuid
force_avb=0
get_current_slot=if part number mmc ${mmcdev} misc control_part_number; then ec;
get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}
get_fdt_usb=load usb ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
get_fit_mmc=load mmc ${bootpart} ${addr_fit} ${bootdir}/${name_fit}
get_fit_usb=load usb ${bootpart} ${addr_fit} ${bootdir}/${name_fit}
get_kern_mmc=load mmc ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_kern_usb=load usb ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_overlay_mmc=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name;
get_overlay_usb=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name;
get_overlaystring=for overlay in $name_overlays;do;setenv overlaystring ${overl;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t $}
init_mmc=run args_all args_mmc
init_usb=run args_all args_usb
kernel_addr_r=0x82000000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefi}
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
mmcboot=mmc dev ${mmcdev}; devnum=${mmcdev}; devtype=mmc; if mmc rescan; then e;
mmcdev=1
mmcloados=if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run load;
mmcrootfstype=ext4 rootwait
name_fit=fitImage
name_kern=Image
partitions=uuid_disk=${uuid_gpt_disk};name=bootloader,start=5M,size=8M,uuid=${u}
partitions_android=uuid_disk=${uuid_gpt_disk};name=bootloader,start=5M,size=8M,}
pxefile_addr_r=0x80100000
ramdisk_addr_r=0x88080000
rd_spec=-
rdaddr=0x88080000
run_fit=bootm ${addr_fit}#${fdtfile}${overlaystring}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env et
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixee
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${e
scriptaddr=0x80000000
serial#=0000000000000174
set_android_boot=setenv android_boot 1;setenv partitions $partitions_android;se;
soc=k3
stderr=serial@2800000
stdin=serial@2800000
stdout=serial@2800000
update_to_fit=setenv loadaddr ${addr_fit}; setenv bootfile ${name_fit}
usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boi
usbboot=setenv boot usb;setenv bootpart 0:2;usb start;run findfdt;run init_usb;n
uuid=28016719-02
vendor=ti

Environment size: 14236/131068 bytes

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Which SDK you are trying to boot here?

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

hi,

my SDK version is -09_01_00_08

software-dl.ti.com/.../Overview.html

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Pavithra P said:
my SDK version is -09_01_00_08

software-dl.ti.com/.../Overview.html

Then please use the U-Boot images that comes with this Linux SDK. The previously shared environment variables from U-Boot looks like for booting Android SDK.

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

hi,

Ok.i am using belena etcher flash tool with SD card using my build linux image was flashed But booting time this issue is came.Gpt Error?

GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
gpt_verify_headers: *** ERROR: Invalid GPT ***
Verify GPT: error!
Broken MMC partition scheme
Running Fastboot...

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Pavithra P said:
my build linux image was flashed

How are you generating your linux image for SD card?

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

hii,

my linux build image (.wic.xz image) was flashed sucessfully using belana etcher flash tool through the SD card

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Hello,

I understand that. I would like to know how are you creating this .wic.xz image?

0 Pavithra P over 2 years ago in reply to Prashant Shivhare

Prodigy 110 points

Hello,

1) For AM62x board We are now trying to flash an Android prebuilt image version (09.01.00)to an SD card through eMMC, and the flashing is completed successfully with full booting.

2)However, when flashing a Yocto prebuilt image version (08.03.00.19) using the Balena Etcher flash tool to the SD card, a GPT error occurs.How to solve this issue ?

GPT Error i mentioed below:

============================

Board: AM62-SKEVM rev E3
DRAM: 2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
gpt_verify_headers: *** ERROR: Invalid GPT ***
Verify GPT: error!
Broken MMC partition scheme
Running Fastboot...

logs of above command:

=> printenv loadaddr
loadaddr=0x82000000
=> printenv mmcdev
mmcdev=1
=> printenv bootpart
bootpart=1:2
=> mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
=> mmc part

Partition Map for MMC device 0 --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
1     0x00002800      0x000067ff      "bootloader"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   9626e7bb-f8b3-1045-8a26-8a514ff926bc
2     0x00002000      0x000027ff      "tiboot3"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   7b5d4b3b-06e6-9542-912a-7b602d1918a2
3     0x00006c00      0x00006fff      "misc"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   28ccac00-a666-1442-898b-d643d6a043c5
4     0x00007000      0x0001afff      "boot_a"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   a58a623e-0dd8-d047-beb2-4e0836a3321c
5     0x0001b000      0x0002efff      "boot_b"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   4e0e8f96-0d68-604c-80cd-fedb4758974b
6     0x0002f000      0x0003efff      "vendor_boot_a"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   42d15dd5-e560-4442-9fce-630fe3a5baa1
7     0x0003f000      0x0004efff      "vendor_boot_b"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   c27f5fbd-8459-1845-96fa-c0ab3f7bde26
8     0x0004f000      0x00052fff      "init_boot_a"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   cea287b6-1b1c-5445-a7f8-6a0110d5a893
9     0x00053000      0x00056fff      "init_boot_b"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   3d053e95-ac3e-c04d-8b8b-e0c023eba1e3
10     0x00057000      0x0005afff      "dtbo_a"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   3dd32867-6508-4343-a92b-ccdf91f0950c
11     0x0005b000      0x0005efff      "dtbo_b"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   4d0968cd-e065-624f-a4e3-625e8b3fd241
12     0x0005f000      0x0005f07f      "vbmeta_a"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   2dac3227-7db3-d648-9453-80f04d73a7a4
13     0x0005f080      0x0005f0ff      "vbmeta_b"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   1be455ac-3d84-bb42-8dbe-8a666cdb2319
14     0x0005f100      0x0095f0ff      "super"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   43fd9337-74ba-c24a-8c23-c3017daaf0d1
15     0x0095f100      0x009670ff      "metadata"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   6925418b-6121-e34c-9da9-b698f3dd38fe
16     0x00967100      0x009770ff      "persist"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   d02d515d-479e-3a4f-883f-b197a8924cb8
17     0x00977100      0x01da3fde      "userdata"
        attrs: 0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   a74f15a3-bc9e-fa41-bf59-416dc0c2ad89
=> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
=> mmc part

Partition Map for MMC device 1 --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
1     2048            271558          7f00581c-01     0c Boot
2     274432          5780880         7f00581c-02     83

=> run args_mmc

=> printenv bootargs
bootargs=console=ttyS2,115200n8 root=PARTUUID=7f00581c-02 rw rootfstype=ext4 rootwait

=> mmc list
mmc@fa10000: 0 (eMMC)
mmc@fa00000: 1 (SD)
mmc@fa20000: 2

=> printenv partitions
partitions=uuid_disk=${uuid_gpt_disk}name=bootloader,start=5M,size=8M,uuid=${uuid_gpt_bootloader};name=tiboot3,start=4M,size=1M,uui}
=> printenv bootargs
bootargs=console=ttyS2,115200n8 root=PARTUUID=0f6b8b27-02 rw rootfstype=ext4 rootwait
=> printenv bootcmd
bootcmd=run distro_bootcmd
=>

0 Prashant Shivhare over 2 years ago in reply to Pavithra P

TI__Guru* 86011 points

Hello,

It seems like you are trying to boot an Android image. In that case, please create a separate thread so that it could be assigned to the Android expert.

Thanks!

Processors

Processors forum

SK-AM62X-BOOT ISSUE