• State TI Thinks Resolved
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 70 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

PROCESSOR-SDK-AM62A: Boot stack when I use "tiboot3-am62ax-gp-evm.bin"

Ryuuichi machida
Guru 12005 points
Part Number: PROCESSOR-SDK-AM62A

Tool/software:

Hi,

I'm trying to use Linux SDK "10.01.00.05" of AM62A on EVM.
At first, I'm importing "wic" information to SD card, and boot it.
Then I got following error.

---
U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
Trying to boot from MMC2
Error reading cluster
spl_load_image_fat: error reading image u-boot.img, err - -22
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
---

So, I changed default "tiboot3.bin" from "tiboot3-am62ax-gp-evm.bin" by following below URL information.

https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/docs/linux/Foundational_Components_Migration_Guide.html
To boot on GP devices, use ‘tiboot3-am62ax-gp-evm.bin’ found in the Processor SDK. If using SD/MMC boot and having flashed a .wic image (WIC file) to an SD card, ‘tiboot3-am62ax-gp-evm.bin’ should be found in the boot partition of the SD card. Renaming/removing the pre-existing tiboot3.bin and renaming ‘tiboot3-am62ax-gp-evm.bin’ to tiboot3.bin is the only change needed to boot the HS-FS device.

However, after that, I could not see any log on console when booting up.
When I use SDK 09.02.00.05, I could boot by appling above method.

I'm using a little bit old EVM (Printed "PROC135E2" on EVM), is it root cause of this issue ?
Or is there any other procedure to boot GP device(implemented on EVM) ?

Best Regards,

  • 0
    TI__Guru 50295 points

    Hello,

    Ryuuichi machida said:
    ### ERROR ### Please RESET the board ###

    This doesn't look like a GP vs. HS-FS issue. It's probably an SD card issue. Please try a different card or even a different brand. In our tests, the Sandisk brand has the most reliable SD cards.

    Ryuuichi machida said:
    However, after that, I could not see any log on console when booting up.

    This is most likely the GP vs. HS-FS issue. If you boot the board with wrong type of device, you wont' see any log.

    Regards,

    Jianzhong

  • 0 in reply to Jianzhong Xu
    Guru 12005 points

    Hi,

    >Please try a different card or even a different brand. In our tests, the Sandisk brand has the most reliable SD cards.
    I'm trying to following test.

    1. I'm flashing "wic" file of "SDK version 09.02.00.05"
    2. I'm flashing "wic" file of "SDK version 10.00.00.08"
    3. I'm flashing "wic" file of "SDK version 10.01.00.05"
    Note : I used same SD card for above contents.

    Here is result.
    For 1. I could confirm boot up correctly.
    For 2. I saw following error and could NOT confirm boot up correctly.
    For 3. Same condition as above "2".

    ---Log for "2"---
    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: 13568 bytes
    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_image_fat: error reading image u-boot.img, err - -22
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###
    ----
    ----Log for "3" ---

    U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
    SPL initial stack usage: 13568 bytes
    Trying to boot from MMC2
    Authentication passed
    Authentication passed
    Authentication passed
    Authentication passed
    Authentication passed
    Starting ATF on ARM64 core...

    NOTICE: BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
    NOTICE: BL31: Built : 04:20:32, Nov 1 2024

    U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
    Trying to boot from MMC2
    Error reading cluster
    spl_load_image_fat: error reading image u-boot.img, err - -22
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###
    ----

    It seems that this issue is related to later SDK 10 and TI AM62A EVM Rev PROC135E2.
    Could you confirm you can see same phenomenon ?

    Best Regards,

  • 0 in reply to Ryuuichi machida
    TI__Guru 50295 points

    Yes, when I used a non-compatible SD card, I saw the same log. 

    Please some SanDisk cards like this one: www.amazon.com/.../ref=ppx_yo_dt_b_search_asin_title

  • 0 in reply to Jianzhong Xu
    Guru 12005 points

    Hello,

    Today, I tried following two SD card in addition to yesterday's one (I used "Gigastone" one at first).

    1. KIOXIA 32GB SDHC UHS-I (I bought this SD card today)
    2. SanDisk 32GB SDHC UHS-I (I had this before)

    When I performed boot by using KIOXIA one at first, I observed same error as previous one.
    However, when I performed boot by using SanDisk one, I could confirm boot correctly.

    KIOXIA and Gigastone one can be used for earlier than SDK 10.
    If something change from view point of SD boot later SDK 10, could you tell me more detail ?

    Best Regards, 

  • 0 in reply to Ryuuichi machida
    TI__Guru 50295 points

    Please check the release notes to find the differences between SDK 9.x and 10.1: software-dl.ti.com/.../Release_Specific_Release_Notes.html