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-AM64X: Boot via USB DFU Fails

Part Number: PROCESSOR-SDK-AM64X

Dear TI Support,

I'm trying to boot my AM64 dev board via USB DFU. I'm following this guide: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/08_05_00_21/exports/docs/linux/Foundational_Components/U-Boot/UG-DFU.html

I did not build the bootloader files. Instead I'm using the prebuild files from am64xx-evm-linux-sdk-bin-08.05.00.21.tar.xz. I did set the SYSBOOT switches to usb boot and removed the jumper on J23.

I can correctly list the dfu endpoints before uploading anything. Uploading tiboot3.bin looks fine on the command line. Afterwards no more DFU endpoints are discovered and I can not proceed to upload the remaining files.

$ ~/ti/test/sdk-8.5-bin# dfu-util -l
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 http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0451:6165] ver=0200, devnum=78, cfg=1, intf=0, path="1-1", alt=0, name="bootloader", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=78, cfg=1, intf=0, path="1-1", alt=1, name="SocId", serial="01.00.00.00"
$ ~/ti/test/sdk-8.5-bin# dfu-util -R -a bootloader -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 http://sourceforge.net/p/dfu-util/tickets/

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%       577147 bytes
Download done.
DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
dfu-util: can't detach
Resetting USB to switch back to Run-Time mode
$ ~/ti/test/sdk-8.5-bin# dfu-util -l
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 http://sourceforge.net/p/dfu-util/tic

However, on the UART output I can see that there are some problems with the k3_system_controller and ti_sci:

U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 18:25:27 +0000)
k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
Firmware init failed on rproc (-110)

resetting ...
ti_sci dmsc@44043000: ti_sci_get_response: Message receive failed. ret = -110
ti_sci dmsc@44043000: ti_sci_get_response: Message receive failed. ret = -110
ti_sci dmsc@44043000: ti_sci_get_response: Message receive failed. ret = -110
System reset not supported on this platform
### ERROR ### Please RESET the board ###

I'm using the AM64x GP EVM (PROC101B), Linux SDK 8.5.

A bit of background: I also tried uploading the precompiled bootloader from an older SDK (SDK 8.1) and this worked fine. I was able to upload all 3 files and boot up to the u-boot prompt. However, when I manually compile u-boot from SDK 8.1 src and upload the resulting binaries, I get similar errors as mentioned above.

Kind Regards,

Eric Opitz