• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 705 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.

PROCESSOR-SDK-AM62X: DFU Util not recognising the device

swapna I
Intellectual 400 points

Part Number: PROCESSOR-SDK-AM62X

Hi,

Iam having AM62x Evaluation kit. Im trying to flash eMMC using dfu-util. Iam following the link

https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_06_00_42/exports/docs/linux/Foundational_Components/U-Boot/UG-DFU.html#usb-device-firmware-upgrade-label

I have installed the dfu-util. but when I try to send the command "sudo dfu-util -l"   , the name and serial number is coming as 'UNKNOWN'.

please let us know how to fix this issue. attaching the screen shot

administrator@administrator-Latitude-7400:~/ti-processor-sdk-linux-am62xx-evm$ sudo dfu-util -l
[sudo] password for administrator:
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/.../

Found DFU: [0451:6165] ver=0200, devnum=19, cfg=1, intf=0, path="1-2", alt=1, name="UNKNOWN", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0200, devnum=19, cfg=1, intf=0, path="1-2", alt=0, name="UNKNOWN", serial="UNKNOWN"
administrator@administrator-Latitude-7400:~/ti-processor-sdk-linux-am62xx-evm$

Thanks and Regards,

Swapna.

  • 0
    TI__Expert 8520 points

    Hi,

    I have not seen this before. The error makes me think you are missing some dependencies for dfu-util since you are facing issues while listing the available DFU Interfaces. Have you used dfu-util successfully on this Linux machine?

    ~ Judith

  • 0 in reply to Judith Mendez
    Intellectual 400 points

    Hi Judith,

    I had used dfu-util successfully on the same linux machine.

    I was able to successfuly send boot files and file system using following commands. 

    commands from host:

    sudo dfu-util -l

    sudo dfu-util -R -a bootloader -D tiboot3.bin

    sudo dfu-util -R -a tispl.bin -D tispl.bin

    sudo dfu-util -R  -a u-boot.img -D u-boot.img

    commands from target:

    => env default -f -a

    => setenv dfu_alt_info ${dfu_alt_info_emmc}

    => pri dfu_alt_info

    => dfu 0 mmc 0

    then commands from host:

    sudo dfu-util -l

    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

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

    commands from target:

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


    we powered off and changed boot mode switches to eMMC boot, but it was not booting up and no messages seen on console.
    we changed the boot mode switches to SDcard boot. and send following commands.

    => setenv mmcdev 0
    => setenv bootpart 0

    we powered off and changed boot mode switches to eMMC boot, but it was not booting up and no messages seen on console.


    So we thought of repeating above process. changed boot mode switches to USB peripheral boot, and this time DFU-Util is not working and its showing unknown as mentioned.
    in previous post.

    Few observartions from target device is:
    1. if I keep switches in emmc mode, nothing is coming in console.
    2. if I keep in sd card mode, messages coming but it shows booting from MMC 0(emmc) and un recognised file system. and then stuck in between. not coming till point we give password root.
    3. later using balencher I flashed sdk again. now SD card mode is proper
    4. but when I keep switches in USB peripheral mode, dfu-util not working...

    I tried to uninstall dfu-util and then installed again. still the issue not resolved.

    Thanks and Regards,

    Swapna.




  • 0 in reply to swapna I
    Intellectual 400 points

    Hi Judith,

    There was issue with USB type C cable. when we used other cable DFU Util started working.

    we are able to successfully download U-boot images  and tisdk-base.ext4

    and we send the following commands to boot from eMMC

    => setenv mmcdev 0
    => setenv bootpart 0

    power off the device, changed boot mode switches to eMMC boot. we get following error.

    U-Boot SPL 2021.01-00002-g93da3fa57b (Jul 03 2023 - 10:27:32 +0530)
    SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
    SPL initial stack usage: 13424 bytes
    Trying to boot from MMC1
    spl: could not initialize mmc. error: -19
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###.

    attaching log file from target.

    Fullscreen new 123.txt Download 
    U-Boot SPL 2021.01-00002-g93da3fa57b (Jul 03 2023 - 10:27:32 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 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
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

init_env from device 10 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00002-g93da3fa57b (Jul 03 2023 - 10:27:08 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...


U-Boot 2021.01-00002-g93da3fa57b (Jul 03 2023 - 10:27:08 +0530)

SoC:   AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-SKEVM rev E3
DRAM:  2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
=>
=>
=> env default -f -a
## Resetting to default environment
=> pri dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;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
=> editenv dfu_alt_info_emmc
edit: rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;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
=> pri dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;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}
=> pri dfu_alt_info
dfu_alt_info=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;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
=> dfu 0 mmc 0
##DOWNLOAD ... OK
Ctrl+C to exit ...
####DOWNLOAD ... OK
Ctrl+C to exit ...
####DOWNLOAD ... OK
Ctrl+C to exit ...
################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################DOWNLOAD ... OK
Ctrl+C to exit ...
=> setenv mmcdev 0
=> setenv bootpart 0
=> ð
U-Boot SPL 2021.01-00002-g93da3fa57b (Jul 03 2023 - 10:27:32 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC1
spl: could not initialize mmc. error: -19
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

    please help us in fixing the issue.

    Thanks and Regards,
    Swapna.

  • 0 in reply to swapna I
    TI__Expert 8520 points

    Hi,

    Based on the error, it seems like mmc initialization failed.

    However, since this is a different issue, please open a new e2e thread. Thank you.

    ~ Judith