• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 663 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: Failed to boot from USB DFU boot

prince diwan
Prodigy 170 points
Part Number: AM625

We are following above 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

after uploading 3 images getting below 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 failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
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
MMC: no card present
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


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 ${dfu_alt_info_emmc}
=> dfu 0 mmc 0
generic_phy_get_bulk : no phys property

after that apply above 2 last commands and it will stuck in "dfu 0 mmc 0" command.

  • +1
    TI__Guru**** 169071 points

    Hi Prince,

    What is your final goal, to boot Linux from DFU or flashing eMMC/OSPI from DFU?

    prince diwan said:
    => setenv dfu_alt_info ${dfu_alt_info_emmc}
    => dfu 0 mmc 0

    Until you run these two commands, DFU boot is already done and you have the U-Boot prompt.

    These two commands are to get ready to flash eMMC, and waiting for the host to send the images to be flashed to eMMC.

  • 0 in reply to Bin Liu
    Prodigy 170 points

    Hi Bin Liu,

    i am trying to do flashing eMMC/OSPI from DFU.

    for that i follow below steps Please tell me its correct or not.

    First i set my EVM board switch mode to "USB Peripheral boot".

    than I change this defconfig "am62x_evm_r5_usbdfu_defconfig" to Create DFU images.

    After that i apply this 3 commands in host pc 

    • sudo dfu-util -R -a bootloader -D tiboot3-am62x-gp-evm.bin
    • sudo dfu-util -R -a tispl.bin -D tispl.bin
    • sudo dfu-util -R -a u-boot.img -D u-boot.img

    After Upload this 3 images i getting logs in minicom as i mentioned in previous(above) FAQ:

    after uploading u-boot image i press any key and i show this type of command prompt("=>").  

    means i entered  into u-boot mode.

    in this mode i apply bellow 2 commands.

    => setenv dfu_alt_info ${dfu_alt_info_emmc}
    => dfu 0 mmc 0

    whenever i apply this "dfu 0 mmc 0" command i getting output like this "generic_phy_get_bulk : no phys property" and u-boot command prompt is gone.

    i think its waitting for some event.

    at this point i am confuse should i change 

    my EVM board switch mode to "eMMC boot" 

    and create below 4 images by changing this defconfig "am62x_evm_r5_defconfig"

    • tiboot3.bin
    • tispl.bin
    • u-boot.img
    • rootfs.ext4

    after that apply below command

    • sudo dfu-util -a tiboot3.bin.raw -D <your_tiboot3.bin>
    • sudo dfu-util -a tispl.bin.raw -D <your_tispl.bin>
    • sudo dfu-util -a u-boot.img.raw -D <your_u-boot.img>
    • sudo dfu-util -a rootfs -D <your_rootfs.ext4>

    Please tell me above steps are right ? 

  • 0 in reply to Bin Liu
    Prodigy 170 points

    yes you are right but i able to proceed further but i am getting error while uploading rootfs.

    i have followed below steps 

    • sudo dfu-util -a tiboot3.bin.raw -D <your_tiboot3.bin>
    • sudo dfu-util -a tispl.bin.raw -D <your_tispl.bin>
    • sudo dfu-util -a u-boot.img.raw -D <your_u-boot.img>
    • sudo dfu-util -a rootfs -D <your_rootfs.ext4>

    Please find below logs.

    sudo dfu-util -a rootfs -D tisdk-base.ext4
    dfu-util 0.9

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

    dfu-util: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
    Opening DFU capable USB device...
    ID 0451:6165
    Run-time device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Setting #1 ...
    Determining device status: state = dfuIDLE, status = 0
    dfuIDLE, continuing
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download [ ] 0% 13185024 bytes failed!
    state(10) = dfuERROR, status(14) = Something went wrong, but the device does not know what it was

  • 0 in reply to prince diwan
    TI__Guru**** 169071 points

    Hi Prince,

    prince diwan said:
    sudo dfu-util -a rootfs -D tisdk-base.ext4

    Before running this command, what is the output of command "sudo dfu-util -l" on your PC?

  • 0 in reply to Bin Liu
    Prodigy 170 points

    Hi ,

    It will resolve you will close this tickit