This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62B: The board cannot be started using the tisdk-tiny-image compiled by myself.

Part Number: SK-AM62B

Hi team,

In SDK8.6 for AM62x, I succeed buid  tisdk-tiny-image using yocto.

I use balenEther tool and flash "tisdk-tiny-image-am62xx-evm.wic.xz" to SD card.

then I download "k3-am625-sk.dtb" , "Image" and "fitImage" in root/boot

and then I unzip "modules-am62xx-evm.tgz" to root/lib

but it can't boot linux, and reboot repeatly, here is the log:

U-Boot SPL 2021.01-g2ee8efd654 (Sep 26 2023 - 08:47:27 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 08:36:18, Sep 26 2023

U-Boot SPL 2021.01-g2ee8efd654 (Sep 26 2023 - 08:38:34 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2021.01-g2ee8efd654 (Sep 26 2023 - 08:38:34 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62B-SKEVM rev A
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
Unidentified board claims AM62B-SKEVM in eeprom header
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
1490 bytes read in 3 ms (484.4 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 3 ms (0 Bytes/s)
Already setup.
2097152 bytes read in 26 ms (76.9 MiB/s)
55666 bytes read in 4 ms (13.3 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 000000008feef000, end 000000008fffffff ... OK

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
elr: 000000000382f000 lr : 0000000080802d1c (reloc)
elr: 0000000082f40000 lr : 00000000fff13d1c
x0 : 000000008feef000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000082000000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 00000000f7ee6980 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 00000000f7ef0df6
x14: 00000000f7ee6980 x15: 00000000fff1323c
x16: 00000000fff48814 x17: 0000000000000000
x18: 00000000f7ef0de0 x19: 00000000fffe4ef8
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 00000000f7f0b2c8
x24: 00000000f7f0b2c8 x25: 00000000fffceda0
x26: 0000000000000000 x27: 00000000fff13d44
x28: 00000000f7f0b2f0 x29: 00000000f7ee5800

Code: f0e20f1d f0e20f1d f0e20f1d f0e20f1d (ffffffff)
Resetting CPU ...

resetting ...

U-Boot SPL 2021.01-g2ee8efd654 (Sep 26 2023 - 08:47:27 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 08:36:18, Sep 26 2023

U-Boot SPL 2021.01-g2ee8efd654 (Sep 26 2023 - 08:38:34 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2021.01-g2ee8efd654 (Sep 26 2023 - 08:38:34 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62B-SKEVM rev A
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
Unidentified board claims AM62B-SKEVM in eeprom header
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
1490 bytes read in 3 ms (484.4 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 2 ms (0 Bytes/s)
Already setup.
2097152 bytes read in 26 ms (76.9 MiB/s)
55666 bytes read in 5 ms (10.6 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 000000008feef000, end 000000008fffffff ... OK

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
elr: 000000000382f000 lr : 0000000080802d1c (reloc)
elr: 0000000082f40000 lr : 00000000fff13d1c
x0 : 000000008feef000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000082000000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 00000000f7ee6980 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 00000000f7ef0df6
x14: 00000000f7ee6980 x15: 00000000fff1323c
x16: 00000000fff48814 x17: 0000000000000000
x18: 00000000f7ef0de0 x19: 00000000fffe4ef8
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 00000000f7f0b2c8
x24: 00000000f7f0b2c8 x25: 00000000fffceda0
x26: 0000000000000000 x27: 00000000fff13d44
x28: 00000000f7f0b2f0 x29: 00000000f7ee5800

Code: f0e20f1d f0e20f1d f0e20f1d f0e20f1d (ffffffff)
Resetting CPU ...

resetting ...

Are there any problems with the above steps?

And I have some questions about Image and fitImage. For HS-FS boards, do I only need fitImage?

Can you hep me to slove this problem?

Best Regards,

Zane

  • Are there any problems with the above steps?

    Does it work for you when you build the `base` image?

    And I have some questions about Image and fitImage. For HS-FS boards, do I only need fitImage?

    For HS-FS, you should only need the FIT image, with the default U-Boot ENV I believe (you can always double-check the environment via `env print` to follow exactly what the boot is doing).

    Regards, Andreas

  • Hi Andreas,

    You are right! I checked envprint,

     

    bootcmd=run distro_bootcmd
    
    distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
    
    boot_targets=linux fastboot recovery system panic
    
    bootcmd_linux=if test "${android_boot}" -eq 0; then;run findfdt; run envboot; run init_${boot}; run boot_rprocs;if test ${boot_fit} -eq 1; then;run get_fit_${boot}; run get_fit_${boot}; run get_overlaystring; run run_fit;else;run get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern;fi;fi

    So I edit boot_targets:

    => editenv boot_targets
    edit: linux
    => boot

    Now it can start kernel and filesystem, thanks for your help!

    Best Regards,

    Zane