Odrivetool dfu 'waiting to connect' if switch in dfu position

Support
1

Running S1, serial 386234773539, firmware version v0.6.6, and attempting to update to v0.6.8. With switch in ‘run’ position, Anaconda odrivetool and web GUI work well. In ‘run’, odrivetool dfu begins the configuration process but hangs as shown:
“(base) C:\Users\Fuji>odrivetool dfu
ODrive control utility v0.6.7
Waiting for ODrive…
Checking online for latest ODrive S1 firmware on channel master…
Found compatible firmware (0.6.8). Install now? [Y/n] y
Downloading firmware…
The device may have user configuration that will be lost after the firmware upgrade. If you want to back this up please run odrivetool backup-config first. Do you want to continue anyway? [Y/n] y
Putting device 386234773539 into DFU mode…
Still waiting for the device to reappear.
Use the Zadig utility to set the driver of ‘STM32 BOOTLOADER’ to libusb-win32.
Still waiting for the device to reappear.
Use the Zadig utility to set the driver of ‘STM32 BOOTLOADER’ to libusb-win32.
Still waiting for the device to reappear.
Use the Zadig utility to set the driver of ‘STM32 BOOTLOADER’ to libusb-win32.”

Is the Zadig utility still required?
Thank you.

2

Continued. Used Zadig to assign the libusb-win32 driver to the S1 when switch is ‘dfu’. Power cycled the S1. Ran odrivetool dfu under Anaconda. Get:
ODrive control utility v0.6.7
Waiting for ODrive…

NoBackendError Traceback (most recent call last)
→ 172 asyncio.run(odrive.dfu.lauch_dfu(
…
→ 1309 raise NoBackendError(‘No backend available’)

3

Hi JSBatch,

In Zadig, did you specifically select “reinstall driver” with the libusb-win32 driver? You may need to reboot your computer and specifically disconnect and reconnect the ODrive S1.

Alternatively, if you have a Linux computer, this overall process may go smoother – Windows is not very well set up for varied USB communications, unfortunately.

4

Thank you, solomondg.
I take it that, yes, using Zadig is the required procedure.
I will do as you say - will update with a result.