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: SDK10.0 WIC Image Boot Problem

Part Number: SK-AM62A-LP

Tool/software:

Hi Team,

I just downloaded the wic.xz image for SDK10 to an SD card and connected to my SK-AM62A-LP board. Upon boot, it looks like the board gets to a u-boot prompt, but then finds no partition table:

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
Authentication passed
Authentication passed


U-Boot 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)

SoC:   AM62AX SR1.0 HS-FS
Model: Texas Instruments AM62A7 SK
DRAM:  2 GiB (effective 4 GiB)
Core:  87 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
** No partition table - mmc 1 **
** No partition table - mmc 1 **
Couldn't find partition mmc 1:2
Can't set block device
** No partition table - mmc 1 **
Couldn't find partition mmc 1:2
Can't set block device
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Bad Linux ARM64 Image magic!
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'mmc 1' failed
Loading Boot0001 'mmc 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fa00000.bootdev':
Scanning bootdev 'mmc@fa10000.bootdev':
Bus usb@31100000: generic_phy_get_bulk : no phys property
Register 1000840 NbrPorts 1
Starting the controller
USB XHCI 1.10
scanning bus usb@31100000 for devices... 1 USB Device(s) found
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete.

I've never run into an error like this before--could this be a HW issue with my board? (

I've tried re-flashing the SD card, re-downloading the wic image on a different PC and flashing there, but always have the same result.

Best regards,

-RT

  • Hi,

    Could you try a different version wic image?

    Regards,
    Aparna

  • Yes--I just tried a fresh download of SDK9.2, and it boots without issue!

    -RT

  • Hi Aparna, 

    Can you provide any other suggestions? I'm wanting to use SDK10.0 for the integrated Wi-Fi driver.

    BR,

    -RT

  • Hi Aparna,

    I just tried loading the image to a new SD card and saw this error message on boot:

    Is this a different hardware issue?

    -RT

  • Hello Ryan,

    The latest issue that you have shared is due to using an incompatible SD card. Please stick to using the previous one as that worked without this error.

    The error logs shared previously indicates that EFI bootflow is getting used, instead of the legacy bootflow.

    So, you can either create a folder structure manually like below in the boot partition of SD card:

    ├── EFI
    │ └── BOOT
    │ ├── bootaa64.efi
    │ └── grub.cfg
    ├── Image
    ├── tiboot3.bin
    ├── tiboot3-j784s4-gp-evm.bin
    ├── tiboot3-j784s4-gp-evm-j784s4-evm-k3r5-2024.04+git-r0_tisdk_5_edgeai_4.bin
    ├── tiboot3-j784s4-hs-evm.bin
    ├── tiboot3-j784s4-hs-fs-evm.bin
    ├── tispl.bin
    ├── u-boot.img
    ├── uEnv.txt
    └── version

    You can copy the EFI folder from root partition in root/boot/EFI to the boot partition:


    Regards,
    Aparna

  • Hi Aparna,

    I copied the EFI folder from the rootfs partition (rootfs/boot/EFI) into the BOOT partition, but no luck:

    I still get the same "EFI Boot manager: Cannot load any image" prompt in the terminal:

    U-Boot 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)
    
    SoC:   AM62AX SR1.0 HS-FS
    Model: Texas Instruments AM62A7 SK
    DRAM:  2 GiB (effective 4 GiB)
    Core:  87 devices, 30 uclasses, devicetree: separate
    MMC:   mmc@fa10000: 0, mmc@fa00000: 1
    Loading Environment from nowhere... OK
    In:    serial@2800000
    Out:   serial@2800000
    Err:   serial@2800000
    Net:   eth0: ethernet@8000000port@1
    Hit any key to stop autoboot:  0 
    switch to partitions #0, OK
    mmc1 is current device
    ** No partition table - mmc 1 **
    ** No partition table - mmc 1 **
    Couldn't find partition mmc 1:2
    Can't set block device
    ** No partition table - mmc 1 **
    Couldn't find partition mmc 1:2
    Can't set block device
    libfdt fdt_check_header(): FDT_ERR_BADMAGIC
    No FDT memory address configured. Please configure
    the FDT address via "fdt addr <address>" command.
    Aborting!
    Bad Linux ARM64 Image magic!
    Scanning for bootflows in all bootdevs
    Seq  Method       State   Uclass    Part  Name                      Filename
    ---  -----------  ------  --------  ----  ------------------------  ----------------
    Scanning global bootmeth 'efi_mgr':
    No EFI system partition
    No EFI system partition
    Failed to persist EFI variables
    No EFI system partition
    Failed to persist EFI variables
    No EFI system partition
    Failed to persist EFI variables
    No EFI system partition
    Failed to persist EFI variables
    No EFI system partition
    Failed to persist EFI variables
      0  efi_mgr      ready   (none)       0  <NULL>                    
    ** Booting bootflow '<NULL>' with efi_mgr
    Loading Boot0000 'mmc 1' failed
    Loading Boot0001 'mmc 0' failed
    EFI boot manager: Cannot load any image
    Boot failed (err=-14)
    Scanning bootdev 'mmc@fa00000.bootdev':
    Scanning bootdev 'mmc@fa10000.bootdev':
    Bus usb@31100000: generic_phy_get_bulk : no phys property
    Register 1000840 NbrPorts 1
    Starting the controller
    USB XHCI 1.10
    scanning bus usb@31100000 for devices... 1 USB Device(s) found
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete........
    

    Any other suggestions?

    -RT

  • Hi Aparna,

    I'm wanting to show a demo to a customer using SDK10.0. Can you please provide suggestions?

    -RT

  • Hi Ryan, 

    How are you flashing the wic image? 

    And what is the boot mode set?

    Can you confirm these two steps are done correctly.

    Regards,
    Aparna

  • Hi Aparna, 

    Flashing the .wic image using BalenaEtcher and the image comes directly from the product page (SDK 10.00.00.08 tisdk-edgeai-image-am62a-evm.wic.xz.

    Boot mode Switches are [01000000] [11000010] -- set to SD Card boot

    As mentioned before, I'm able to boot SDK 09.02.00.05 without issue and without changing any hardware configuration (only change is the version of SDK that the SD card is flashed with)

    -RT

  • Hi Ryan, 

    Can you confirm the wic image is flashed properly using balena etcher and no error is seen like mentioned in this FAQ:(+) [FAQ] AM62A7-Q1: Balena etcher flash error workaround - Processors forum - Processors - TI E2E support forums

    Regards,
    Aparna