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.

AM62L: eMMC booting issue + PG1.1 using DFU

Part Number: AM62L

Hi, 

I am using an AM62Lx board with a PG1.1 processor.
My processor part number is: XAM62L32B0GHA.

According to the TI thread, PG1.1 should support DFU flashing and then boot from eMMC. However, I am not seeing any logs on the UART console.

I am using the SnapFactory tool to flash the eMMC.

emmc.yaml:

boards:
  "0451:6165": "am62l3"
soc-models:
  am62l3-firmware:
    tiboot3:
      path: "/home/dfu/pp/tiboot3.bin"
    tispl:
      path: "/home/dfu/pp/tispl.bin"
    u-boot:
      path: "/home/dfu/pp/u-boot.img"
  am62l3-tasks:
    - target-device: mmc0
      fb-buffer-addr: 0x82000000
      fb-buffer-size: 0x7000000
    - task: gpt
      args:
        - name: boot
          size: 128M
          bootable: true

 

    - task: flash
      args:
        - image: "/home/dfu/pp/bootfs.img"
          part: boot
    - task: reset
    - task: prompt-operator
      args:
        prompt: "UDA mode complete. Please reboot the board."
        reset-before: false


Best, 
Parv

  • Hello,

    For PG 1.1, you should flash the U-Boot images to the eMMC Boot0 partition instead of the UDA. After flashing, you would then boot from the eMMC using the eMMC alternate bootmode.

  • Hi Prashant, 

    As you mentioned, we verified that the boot configuration is set to eMMC boot and not UDA.

    Below is the sequence of commands I followed:

    HOST PC
    $ sudo dfu-util -l -v
    $ sudo dfu-util -a bootloader -D tiboot3.bin
    $ sudo dfu-util -a bootloader -D tispl.bin
    $ sudo dfu-util -a u-boot.img -D u-boot.img
    
    press CTRL+c at uboot prompt
    
    => setenv dfu_alt_info ${dfu_alt_info_emmc}
    => dfu 0 mmc 0 
    
    HOST PC
    $ sudo dfu-util -a tiboot3.bin.raw -D tiboot3.bin
    $ sudo dfu-util -a tispl.bin.raw -D tispl.bin
    $ sudo dfu-util -a u-boot.img.raw -D u-boot.img
    
    press CTRL+c at uboot prompt
    
    => mmc partconf 0 1 1 1
    => mmc bootbus 0 2 0 0


    After flashing, I changed the board’s boot pin configuration to eMMC Boot0 and powered up the board.

    Upon boot, we encountered the following error:
    NOTICE:  bl1_plat_arch_setup arch setup
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v2.12.0(release):11.00.15-dirty
    NOTICE:  BL1: Built : 12:24:23, May 29 2025
    NOTICE:  BL1: dram_class: 11
    NOTICE:  lpddr4: post start - PI training status=0x27c0a000
    NOTICE:  bl1_platform_setup DDR init done
    NOTICE:  k3_bl1_handoff ENTERING WFI - end of bl1
    NOTICE:  BL31: v2.12.0(release):11.00.15-dirty
    NOTICE:  BL31: Built : 12:24:23, May 29 2025
    NOTICE:  SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.12-v11.00.12 (Fancy Rat)')
    ERROR:   Agent 0 Protocol 0x10 Message 0x7: not supported
     
    U-Boot SPL 2025.01-00464-g1d6ba4a32cdd (May 29 2025 - 19:36:32 +0000)
    SPL initial stack usage: 1872 bytes
    Trying to boot from MMC1
    Partition 1 invalid on device 0
    spl_register_fat_device: fat register err - -1
    spl_load_image_fat: error reading image u-boot.img, err - -1
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###


    Please guide us on what might be causing this issue.

    Best, 
    Parv

  • Hi Parv,

    Upon boot, we encountered the following error:

    That error is expected since the U-Boot is from SDK v11.00.15.05 which does not have the support for eMMC boot partitions as it was released when we had PG1.0 only.

    Now that you have PG1.1, please use the latest SDK and let me know if you still see the issue.

    www.ti.com/.../11.01.16.13