TMDS64EVM: Problems installing SBL DFU Driver on Windows

maasakazu igarashi

Prodigy 20 points

Part Number: TMDS64EVM
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Dear team,

I am working according to 'Getting Started'.

'Download and Install Additional SDK Tools - dfu-util'
$ dfu-util --version
- OK

zadig 2.90
select 'AM64x DFU' and Install WCID Driver
- show 'The driver was installed successfuly.', OK

$ dfu-util -l
> Found DFU: [0451:6165] ver=0200, devnum=34, cfg=1, intf=0, path="3-3", alt=1, name="SocId", serial="01.00.00.00"
> Found DFU: [0451:6165] ver=0200, devnum=34, cfg=1, intf=0, path="3-3", alt=0, name="bootloader", serial="01.00.00.00"
- OK so far

$ dfu-util -a 0 -i 0 -t 64 -D sbl_prebuilt\am64x-evm\sbl_dfu_uniflash.release.tiimage
> dfu-util 0.11
>
> 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/.../
>
> Warning: Invalid DFU suffix signature
> 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
> Warning: Overriding device-reported transfer size
> Copying data from PC to DFU device
> Download [=========================] 100% 321471 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!
- looks OK

But no device named 'AM64x-AM243x DFU' is found, and 'AM64x DFU' is still listed.
(both in zadig and DeviceManager)

I continued working,
In 'Flash a Hello World example using DFU - Flashing the application using USB',
usb_dfu_uniflash.py displays
'All commands from config file are executed !!!'
without any errors, but the SBL doesn't seem to be rewritten.

I think this is because the SBL DFU driver is not installed correctly, but I would like to know the cause and solution.

5 months ago

0 Prashant Shivhare 5 months ago

TI__Mastermind 47841 points

Hello,

maasakazu igarashi said:
In 'Flash a Hello World example using DFU - Flashing the application using USB',
usb_dfu_uniflash.py displays
'All commands from config file are executed !!!'

Could you please share these flashing logs?

Regards,

Prashant

0 maasakazu igarashi 5 months ago in reply to Prashant Shivhare

Prodigy 20 points

Thanks for your reply.

paste the log.

---

C:\ti>cd C:\ti\mcu_plus_sdk_am64x_08_06_00_45\tools\boot

C:\ti\mcu_plus_sdk_am64x_08_06_00_45\tools\boot>dfu-util -l
dfu-util 0.11

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/.../

Found DFU: [0451:6165] ver=0200, devnum=32, cfg=1, intf=0, path="3-3", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=32, cfg=1, intf=0, path="3-3", alt=0, name="bootloader", serial="01.00.00.00"
Found Runtime: [05c8:082f] ver=0010, devnum=2, cfg=1, intf=4, path="3-1", alt=0, name="APP Mode", serial="01.00.00"

C:\ti\mcu_plus_sdk_am64x_08_06_00_45\tools\boot>python usb_dfu_uniflash.py --cfg=sbl_prebuilt/am64x-evm/helloworld_r5_sbl_ospi.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 4 command(s) !!!

Executing command 1 of 4 ...
Found flash writer ... sending sbl_prebuilt/am64x-evm/sbl_dfu_uniflash.release.tiimage
----------------------------------------------------------------------------
Executing DFU command with alt_setting=0 interface=0 transfer_size=512
----------------------------------------------------------------------------
dfu-util 0.11

Executing command 2 of 4 ...
Command arguments : --operation=flash-phy-tuning-data
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
----------------------------------------------------------------------------
Executing DFU command with alt_setting=0 interface=0 transfer_size=512
----------------------------------------------------------------------------
dfu-util 0.11

Warning: Invalid DFU suffix signature
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
Warning: Overriding device-reported transfer size
Copying data from PC to DFU device
Download [=========================] 100% 32 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!
Sent flash phy tuning data in 1.14s.
True
Executing command 3 of 4 ...
Command arguments : --file=sbl_prebuilt/am64x-evm/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
----------------------------------------------------------------------------
Executing DFU command with alt_setting=0 interface=0 transfer_size=512
----------------------------------------------------------------------------
dfu-util 0.11

Warning: Invalid DFU suffix signature
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
Warning: Overriding device-reported transfer size
Copying data from PC to DFU device
Download [=========================] 100% 317407 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!
Sent sbl_prebuilt/am64x-evm/sbl_ospi.release.tiimage of size 317375 bytes in 1.67s. Bandwidth = 185.59kbps
True
Executing command 4 of 4 ...
Command arguments : --file=/Work/TI/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang/Release/hello_world_am64x-evm_r5fss0-0_freertos_ti-arm-clang.appimage --operation=flash --flash-offset=0x80000
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
------------------------------------------------------
Waiting for DFU device to be enumerated ....
------------------------------------------------------
----------------------------------------------------------------------------
Executing DFU command with alt_setting=0 interface=0 transfer_size=512
----------------------------------------------------------------------------
dfu-util 0.11

0 Prashant Shivhare 5 months ago in reply to maasakazu igarashi

TI__Mastermind 47841 points

Hello,

How do you confirm the images are not actually written even though the flashing is successful?

Can you also once check the device type you are working with?

[FAQ] [AM6XX]: How to check if device type is HS-SE, HS-FS or GP? - Processors forum - Processors - TI E2E support forums

Regards,

Prashant

0 maasakazu igarashi 5 months ago in reply to Prashant Shivhare

Prodigy 20 points

Hello,

I switched to OSPI BOOT MODE and checked the string displayed in the UART Terminal.

Initially, "Starting NULL Bootloader ..."
is displayed, and this did not change even when I tried to rewrite it to 'sbl_prebuilt/am64x-evm/sbl_ospi.release.tiimage'.

When another member tried writing, the string displayed in the UART Terminal clearly changed.

> DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
> DMSC Firmware revision 0x9
> DMSC ABI revision 3.1
>
> [BOOTLOADER_PROFILE] Boot Media : NOR SPI FLASH
> [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz
> [BOOTLOADER_PROFILE] Boot Image Size : 0 KB
> [BOOTLOADER_PROFILE] Cores present :
> r5f0-0
> [BOOTLOADER PROFILE] SYSFW init : 12170us
> [BOOTLOADER PROFILE] System_init : 349500us
> [BOOTLOADER PROFILE] Drivers_open : 318us
> [BOOTLOADER PROFILE] Board_driversOpen : 23227us
> [BOOTLOADER PROFILE] Sciclient Get Version : 10028us
> [BOOTLOADER PROFILE] CPU Load : 24256us
> [BOOTLOADER_PROFILE] SBL Total Time Taken : 419506us
>
> Image loading done, switching to application ...
> Run CPU r5f0-0 to 800000000 Hz.

The 'AM64x-AM243x DFU' device is recognized on his PC.

In his usb_dfu_uniflash.py writing log,
> ------------------------------------------------------
> Waiting for DFU device to be enumerated ....
> ------------------------------------------------------
does not repeat.

From the above, I thought that there might be a problem with the driver on my PC.

0 Prashant Shivhare 5 months ago in reply to maasakazu igarashi

TI__Mastermind 47841 points

Hello,

maasakazu igarashi said:
When another member tried writing, the string displayed in the UART Terminal clearly changed.

Was it on the same board or a different one? If it was same board and working on your colleague's PC then this, as you say, might be a problem with your PC only.

Have you tried restarting the PC?

Do you have a Linux PC on which you can try the same procedure?

Regards,

Prashant

0 maasakazu igarashi 5 months ago in reply to Prashant Shivhare

Prodigy 20 points

Thank you for your support. The problem was solved !

I changed the base SDK from 08 to 09.

The referenced configuration file is "sbl_prebuilt/am64x-evm/default_dfu_ospi.cfg"
[SDK 08.06.00] --flash-writer=sbl_dfu_uniflash.release.tiimage
[SDK 09.01.00] --flash-writer=sbl_dfu_uniflash.release.hs_fs.tiimage

When I used the hs_fs version, the AM64x-AM243x DFU device was found and the driver was installed.

After that, I was able to confirm that the hs_fs SBL image was written.

My team members were using hs_fs version.

Thank you very much.

Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

Processors

Processors forum

TMDS64EVM: Problems installing SBL DFU Driver on Windows