• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 656 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.

AM625: emmc boot failed.

prince diwan
Prodigy 170 points
Part Number: AM625

I trying to do emmc flashing with referance of below FAQ : 

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1127618/faq-sk-am62-how-to-flash-emmc-using-usb-dfu-on-am62x-sk-e2#:~:text=A%20type%2DC%20USB%20connector,to%20eMMC%20%28eMMC%20boot%29

I download all the images

but whenever i trying to upload rootfs i am getting error like :   Request would exceed designated area!

so i do some searches and find below commands.

=> setenv dfu_alt_info_emmc 'rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 2;tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sysfw.itb.raw raw 0x3600 0x800 mmcpart 1'
=> setenv dfu_alt_info ${dfu_alt_info_emmc}

after apply this command i upload my rootfs and error will be solved.

after this i apply this two commands according to FAQ.

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

and change the boot switch mode to "emmc boot" and reboot the EVM board.

but after this no logs i getting in minicom.

i can not see any u-boot prompt.

can anyone help me to resolve this ?

  • 0
    TI__Guru 71551 points

    Hi prince,

    Can you check the device type you are working and confirm if you are flashing the correct images?

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 170 points

    Hi ,

    yes it will boot using SD card flash.

  • 0 in reply to prince diwan
    Prodigy 170 points

    but not getting any logs in emmc flash

  • 0 in reply to prince diwan
    TI__Guru 71551 points
    prince diwan said:
    but not getting any logs in emmc flash

    Can you share the DFU flashing logs?

    Can you also share the bootmode switches positions on your board for eMMC boot?

  • 0 in reply to Prashant Shivhare
    Prodigy 170 points

    Host Machine logs

    -->sudo dfu-util -R -a bootloader -D tiboot3-am62x-gp-evm.bin
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #0 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 512
    Copying data from PC to DFU device
    Download [=========================] 100% 307305 bytes
    Download done.
    DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
    dfu-util: unable to read DFU status after completion (LIBUSB_ERROR_IO)

    -->sudo dfu-util -R -a tispl.bin -D tispl.bin
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #0 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [=========================] 100% 1174743 bytes
    Download done.
    DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to Run-Time mode


    -->sudo dfu-util -R -a u-boot.img -D u-boot.img
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #1 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [=========================] 100% 970443 bytes
    Download done.
    DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to Run-Time mode


    -->sudo dfu-util -a tiboot3.bin.raw -D tiboot3.bin
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #2 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [=========================] 100% 309894 bytes
    Download done.
    DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    Done!


    -->sudo dfu-util -a tispl.bin.raw -D tispl.bin
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #3 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [=========================] 100% 1174743 bytes
    Download done.
    DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    Done!

    -->sudo dfu-util -a rootfs -D tisdk-base.ext4
    dfu-util 0.11-dev

    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2021 Tormod Volden and Stefan Schmidt
    This program is Free Software and has ABSOLUTELY NO WARRANTY
    Please report bugs to sourceforge.net/.../

    dfu-util: Warning: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release
    Opening DFU capable USB device...
    Device ID 0451:6165
    Device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Interface #1 ...
    Determining device status...
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [=========================] 100% 1073741824 bytes
    Download done.
    DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
    DFU state(2) = dfuIDLE, status(0) = No error condition is present
    Done!

    Target machine logs

    U-Boot SPL 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
    SPL initial stack usage: 13384 bytes
    Trying to boot from DFU
    ##########################################################DOWNLOAD ... OK
    Ctrl+C to exit ...
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Loading Environment from nowhere... OK
    init_env from device 10 not supported!
    Starting ATF on ARM64 core...

    NOTICE: BL31: v2.9(release):v2.9.0-614-gd7a7135d32-dirty
    NOTICE: BL31: Built : 09:34:15, Aug 24 2023

    U-Boot SPL 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
    SPL initial stack usage: 1856 bytes
    Trying to boot from DFU
    ####DOWNLOAD ... OK
    Ctrl+C to exit ...
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failud


    U-Boot 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)

    SoC: AM62X SR1.0 GP
    Model: Texas Instruments AM625 SK
    EEPROM not available at 80, trying to read at 81
    Board: AM62-SKEVM rev E3
    DRAM: 2 GiB
    Core: 72 devices, 32 uclasses, devicetree: separate
    MMC: mmc@fa10000: 0, mmc@fa00000: 1
    Loading Environment from nowhere... OK
    In: serial
    Out: serial
    Err: serial
    Net: eth0: ethernet@8000000port@1
    Hit any key to stop autoboot: 0
    => setenv dfu_alt_info_emmc 'rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 2;tiboot3.bin.raw raw 0x'
    => setenv dfu_alt_info ${dfu_alt_info_emmc}
    => printenv dfu_alt_info_emmc
    dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 2;tiboot3.bin.raw raw 0x0 0x400 mmc1


    => dfu 0 mmc 0
    generic_phy_get_bulk : no phys property
    ##DOWNLOAD ... OK
    Ctrl+C to exit ...
    #####DOWNLOAD ... OK
    Ctrl+C to exit ...
    ####DOWNLOAD ... OK
    Ctrl+C to exit ...
    ####################################################################################################K
    Ctrl+C to exit ...
    => mmc partconf 0 1 1 1
    => mmc bootbus 0 2 0 0
    Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x0

    We are following below page for EVM switch modes.

    dev.ti.com/.../dev-evm-bootmodesw.html

  • 0 in reply to prince diwan
    TI__Guru 71551 points
    prince diwan said:
    -->sudo dfu-util -a tiboot3.bin.raw -D tiboot3.bin

    You are working with a GP device. And the default tiboot3.bin in the SDK is HSFS one.

    Can you try flashing the GP image:

    sudo dfu-util -a tiboot3.bin.raw -D tiboot3-am62x-gp-evm.bin

  • 0 in reply to Prashant Shivhare
    Prodigy 170 points

    Hi  Prashant Shivhare

    Using above command we successfully getting logs in emmc but now we getting below error 

    U-Boot 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)

    SoC: AM62X SR1.0 GP
    Model: Texas Instruments AM625 SK
    EEPROM not available at 80, trying to read at 81
    Board: AM62-SKEVM rev E3
    DRAM: 2 GiB
    Core: 72 devices, 32 uclasses, devicetree: separate
    MMC: mmc@fa10000: 0, mmc@fa00000: 1
    Loading Environment from nowhere... OK
    In: serial
    Out: serial
    Err: serial
    Net: eth0: ethernet@8000000port@1
    Hit any key to stop autoboot: 0
    => setenv mmcdev 0
    => setenv bootpart 0
    => boot
    switch to partitions #0, OK
    mmc0(part 0) is current device
    SD/MMC found on device 0
    Failed to load 'boot.scr'
    Can't set block device
    ## Error: "main_cpsw0_qsgmii_phyinit" not defined
    Failed to load '/boot/Image'
    60594 bytes read in 17 ms (3.4 MiB/s)
    Working FDT set to 88000000
    Bad Linux ARM64 Image magic!
    switch to partitions #0, OK
    mmc0(part 0) is current device
    Scanning mmc 0:1...
    Working FDT set to 88000000
    MMC: no card present
    No EFI system partition
    No EFI system partition
    Failed to persist EFI variables
    BootOrder not defined
    EFI boot manager: Cannot load any image
    MMC: no card present
    starting USB...
    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
    scanning usb for storage devices... 0 Storage Device(s) found

    Device 0: unknown device
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    missing environment variable: pxeuuid
    Retrieving file: pxelinux.cfg/01-34-08-e1-7e-91-c9
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/00000000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/0000000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/000000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/00000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/0000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/000
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/00
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/0
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/default-arm-k3-am62x
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/default-arm-k3
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/default-arm
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Retrieving file: pxelinux.cfg/default
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
    Config file not found
    ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..!
    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..!
    am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
    am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error

  • 0 in reply to prince diwan
    TI__Guru 71551 points

    Hi Prince,

    You have flashed Linux in 2nd partition. Please refer: e2e.ti.com/.../5127114

  • 0 in reply to Prashant Shivhare
    Prodigy 170 points

    Hi Prashant Shivhare,

    Thanks for your support.

    now i successfully boot from emmc.

    you will close this.