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 boot only once

Part Number: AM62L

Tool/software:

After flash to eMMC, can only boot once,  customer add log in SPL, find it change eMMC boot partition configuration. so can't boot on second power cycle

change to boot up from SD card, modify boot partition, switch back to eMMC boot, can boot up one more time.

=> mmc partconf 0 1 2 1
=> mmc bootbus 0 2 0 0

same result with booting from Boot partition or UDA, Is it intend to do in this way?
  • Tony,

    For AM62L : 

    texasinstruments.github.io/.../UG-Memory-K3.html

    The recommended method is to flash and boot eMMC with MMCSD boot from UDA in fs mode.

  • Hi Praneeth,

    #1. That is two different aspect issue, why UBOOT change eMMC boot parameter which result in can only boot once? this is SW issue, not a silicon issue.

    #2. I tried eMMC FS mode according to the procedure to fdisk UDA to two partition, mkfs mmc0blk1 to fat format, copy tiboot3.bin, tispl.bin u-boot.img from sd card to mmc0blk1, reboot to UBOOT to set: 

    3.1.1.3.1.6.4.3. Boot from UDA
    => mmc partconf 0 1 7 1
    => mmc bootbus 0 2 0 0

    Set boot mode to [0:15] : 11000011 0000 0000 , power up can only boot up with below log, the log is same as DFU boot with default tiboot3.bin. Does it need patch to support eMMC UDA FS boot?

    NOTICE:  bl1_plat_arch_setup arch setup
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v2.12.0(release):11.00.04-10-gdd46885ec-dirty
    NOTICE:  BL1: Built : 05:00:39, Feb 26 2025
    NOTICE:  lpdd4_init <--
    NOTICE:  DDR ram size =80000000
    NOTICE:  bl1_platform_setup DDR init done
    NOTICE:  k3_bl1_handoff ENTERING WFI - end of bl1
    

    And reboot for a while print same log:

    NOTICE:  bl1_plat_arch_setup arch setup
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v2.12.0(release):11.00.04-10-gdd46885ec-dirty
    NOTICE:  BL1: Built : 05:00:39, Feb 26 2025
    NOTICE:  lpdd4_init <--
    NOTICE:  DDR ram size =80000000
    NOTICE:  bl1_platform_setup DDR init done
    NOTICE:  k3_bl1_handoff ENTERING WFI - end of bl1
    NOTICE:  bl1_plat_arch_setup arch setup
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v2.12.0(release):11.00.04-10-gdd46885ec-dirty
    NOTICE:  BL1: Built : 05:00:39, Feb 26 2025
    NOTICE:  lpdd4_init <--
    NOTICE:  DDR ram size =80000000
    NOTICE:  bl1_platform_setup DDR init done
    NOTICE:  k3_bl1_handoff ENTERING WFI - end of bl1
    

    Please provide detail steps to boot from eMMC FS.

    #3. Is the sector name wrong? MMCSD should be eMMC? if yes, hope it be corrected right there, no need to wait next release, and leave the error there forever.

  • 1/. The issue was logged as K3ROM-8417
    2/. I'm attaching a uboot log booting from eMMC UDA/FS with Linux SDK 11.0.5.2 on AM62L EVM for your reference, where BOOTMODE[15:0]=0043 to select eMMC UDA/FS.
    Best,
    -Hong

    NOTICE:  bl1_plat_arch_setup arch setup 
    NOTICE:  Booting Trusted Firmware
    NOTICE:  BL1: v2.12.0(release):11.00.04-10-gdd46885ec-dirty
    NOTICE:  BL1: Built : 05:00:39, Feb 26 2025
    NOTICE:  lpdd4_init <-- 
    NOTICE:  DDR ram size =80000000 
    NOTICE:  bl1_platform_setup DDR init done
    NOTICE:  k3_bl1_handoff ENTERING WFI - end of bl1
    NOTICE:  BL31: v2.12.0(release):11.00.04-10-gdd46885ec-dirty
    NOTICE:  BL31: Built : 05:00:39, Feb 26 2025
    ERROR:   Failed to get response (-19)
    ERROR:   Transfer send failed (-19)
    ERROR:   Agent 0 Protocol 0x10 Message 0x7: not supported
    
    U-Boot SPL 2025.01-00253-g9a3137c5c11a (Feb 26 2025 - 17:07:57 +0000)
    SPL initial stack usage: 1872 bytes
    Trying to boot from MMC1
    ERROR:   Agent 0 Protocol 0x10 Message 0x7: not supported
    
    
    U-Boot 2025.01-00253-g9a3137c5c11a (Feb 26 2025 - 17:07:57 +0000)
    
    SoC:   AM62LX SR1.0 HS-FS
    Model: Texas Instruments AM62L3 Evaluation Module
    DRAM:  2 GiB
    ERROR:   Agent 0 Protocol 0x10 Message 0x7: not supported
    Core:  66 devices, 28 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
    Warning: ethernet@8000000port@2 (eth1) using random MAC address - 12:b3:30:04:a4:46
    , eth1: ethernet@8000000port@2
    Hit any key to stop autoboot:  2  0
    => mmc list
    mmc@fa10000: 0
    mmc@fa00000: 1
    => ls mmc 0
       226016   tiboot3.bin
       762365   tispl.bin
      1181035   u-boot.img
    
    3 file(s), 0 dir(s)
    
    => mmc dev 1
    MMC: no card present
    => mmc dev 0
    switch to partitions #0, OK
    mmc0(part 0) is current device
    => mmc info
    Device: mmc@fa10000
    Manufacturer ID: 13
    OEM: 4e
    Name: G1M15L 
    Bus Speed: 52000000
    Mode: MMC High Speed (52MHz)
    Rd Block Len: 512
    MMC version 5.1
    High Capacity: Yes
    Capacity: 29.6 GiB
    Bus Width: 8-bit
    Erase Group Size: 512 KiB
    HC WP Group Size: 8 MiB
    User Capacity: 29.6 GiB WRREL
    Boot Capacity: 31.5 MiB ENH
    RPMB Capacity: 4 MiB ENH
    Boot area 0 is not write protected
    Boot area 1 is not write protected
    => md.l 0x43010030 1
    43010030: 00000043                             C...
    => mmc partconf 0
    EXT_CSD[179], PARTITION_CONFIG:
    BOOT_ACK: 0x1
    BOOT_PARTITION_ENABLE: 0x7 (user)
    PARTITION_ACCESS: 0x0 (user)
    => 

  • My boot mode is 0xC3, should be yours 0x43.

  • The issue was logged as K3ROM-8417

    Although I did not find the Jira item (actually I don't know how to find). From the name it is ROM issue items. but we think it is UBOOT SW issue.

  • Hi Tony,
    The internal ongoing investigation currently points to the ROM issue.
    Best,
    -Hong