• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 500 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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-AM62A-LP: SD card Image booting failure issue in Linux SDK

Dominic SK
Prodigy 30 points

Part Number: SK-AM62A-LP

Tool/software:

 

Hi TI,

I've been testing the AM62A board since last week.
First, I tried booting using tisdk-edgeai-image-am62axx-evm.wic.xz, the SD card image provided in TI-LINUX-SDK.
When using the image of SDK v10x(19 Aug 2024) and creating an SD card with balenaetcher, 
all boot loader files (tiboo3.bin, tispl.bin, u-boot.img) are present in the boot folder, 
but no message is displayed in the terminal. It appears that booting failed.

When using Linux-SDK v09x SD card image, it failed to boot normally, just like v10x.
This time, I unzipped xz and wrote it to the SD card using win32diskimager, and booting was successful.
 

However, if you write the SD card image of Linux-SDK v08x(27 Feb 2023) using balenaetcher, 
it is confirmed that it boots normally.

 

i am using balenetcher v1.19.25
To successfully boot, first write Linux SDK v10x to the SD card.
Then, just overwrite tispl.bin of Linux SDK v08x on the SD card.
In other words, booting was possible just by replacing tispl.bin.

1) Is there a reason why only the v08x image boots normally when using balenaetcher?

2) Is there a mistake in failing to boot with the v10x image?
Thanks

  • 0
    TI__Guru 70762 points
    Dominic SK said:
    all boot loader files (tiboo3.bin, tispl.bin, u-boot.img) are present in the boot folder,
    but no message is displayed in the terminal. I
    Dominic SK said:
    Then, just overwrite tispl.bin of Linux SDK v08x on the SD card.

    Are you saying you prepared an SDKv10-based SD card and it did not output anything into the terminal window at all?

    And then you replaced tispl.bin with an older version, and then it worked?

    Something doesn't add up here, since tispl.bin is the 2nd stage of the boot loader chain that's loaded from SD card. The first state is tiboot3.bin (a.k.a. "R5 SPL") that also outputs to the console. Replacing the 2nd stage should not magically make the 1st stage work.

    Can you try using another way to program the SD card? Personally I'd not recommend/trust using any windows or "balena etcher" GUI tools; but instead do the programming straight from the command line under Linux using the `bmaptool`.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 30 points

    When writing a V10x image with balenaetcher, no message is output.

    When run with win32diskimager, the output is as follows. 

    U-Boot SPL 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13568bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024

U-Boot SPL 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Trying to boot from MMC2
Error reading cluster
spl_load_iamge_fat: error reading image u-boot.img, err = -22
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###


    In this situation, I overwrite v08x's tispl.bin.
    Then it boots normally.

    What you should not forget is that V08x images work normally whether using balenaetcher or win32diskimager.

  • 0 in reply to Dominic SK
    TI__Guru 70762 points
    Dominic SK said:

    When writing a V10x image with balenaetcher, no message is output.

    When run with win32diskimager, the output is as follows.

    Same image? That is very strange. Hence my suggestion of using the Linux command line tool.

    The other additional thing you can try is using a different brand/model of SD card to see if that makes any difference.

    Regards, Andreas