dfu-util error get_status: LIBUSB_ERROR_INVALID_PARAM failure

[brianvanderbeek-philips]

Hi all,

I am trying to enable HID + DFU on a ST32WB55 MCU using TinyUSB v0.18.0. I defined a device configuration [1] for HID and another device configuration [2] for DFU. HID is functional and I can send out key records, but when using lsusb or dfu-util on Windows both report a that the status cannot be read.

This is the lsusb log, which does correctly show the configuration: 20250724 lsusb log.txt

dfu-utils output:

.\dfu-util.exe --list
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 http://sourceforge.net/p/dfu-util/tickets/

Found Runtime: [0bda:5855] ver=0001, devnum=15, cfg=1, intf=2, path="2-8", alt=0, name="Camera DFU Device", serial="200901010001"
Found DFU: [cafe:20a0] ver=0100, devnum=19, cfg=2, intf=0, path="2-1.3", alt=0, name="Remote Control DFU Device", serial="012345"

.\dfu-util.exe --serial 012345 -a 0 -D firmware.bin
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 http://sourceforge.net/p/dfu-util/tickets/

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 cafe:20a0
Device DFU version 0101
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
error get_status: LIBUSB_ERROR_INVALID_PARAM

So both lsusb or dfu-util return the same get_status error. When I run lsusb on other USB devices I do not get a get status error, altohugh for most it warns that some information will be missing).

It seems odd that dfu-util is able to claim the DFU interface, but for some reason it is not able to retrieve the status. In the TinyUSB log I also do not see a get status entry, so it seems that the libusb_control_transfer call must somehow be failing before initiating the transfer:
https://github.com/Stefan-Schmidt/dfu-util/blob/master/src/dfu.c#L204

    result = libusb_control_transfer( device,
          /* bmRequestType */ LIBUSB_ENDPOINT_IN | LIBUSB_REQUEST_TYPE_CLASS | LIBUSB_RECIPIENT_INTERFACE,
          /* bRequest      */ DFU_GETSTATUS,
          /* wValue        */ 0,
          /* wIndex        */ interface,
          /* Data          */ buffer,
          /* wLength       */ 6,
                              dfu_timeout );

I have been unable to identify what triggers this error on my device. I have been comparing my configuration with others, trying different configurations (e.g. remove HID, move the HID+DFU interface configuration in the same device configurations), but no luck.

Anyone got an idea what might cause this failure?

[brianvanderbeek-philips]

It seems I have found the problem. By default Windows installs the hidusb.sys driver when advertising HID and when advertising DFU only no default driver is being installed. DFU requires the winusb.sys driver. With WCID it should be possible to indicate that Windows must use the winusb.sys driver for the DFU interface.