MCUBOOT serial recovery mode usb not recognised by windows 11 device manager

[JustinL]

Hi,

I am using nrf connect sdk 2.3.0 and have configured mcuboot for serial recovery triggered via pin so my users can update firmware via usb and a windows machine.

When powering on with the pin held low DFU mode is entered as expected.

However, in windows device manager a failed usb device "MCUBOOT" shows up with windows saying there are no drivers for this.

In addition a com port is also added, that appears to be fine. 

When using nrfutil to list devices the trait mcuboot does not appear (device is E60EF9D290C74E49 and shows its serialPorts trait but no mcuboot)

nrfutil device list {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
ports COM7, vcom: 0
COM16, vcom: 1
COM13, vcom: 2
traits serialPorts, usb

E60EF9D290C74E49
ports COM18
traits serialPorts, usb

id:4
ports COM14
traits serialPorts

id:5
ports COM17
traits serialPorts

id:6
ports COM4
traits serialPorts

Any attempt to program the device via nrfutil says programming not supported.

Here is my mcuboot.conf file

CONFIG_BOOT_USB_DFU_GPIO=y

CONFIG_BOOT_USB_DFU_DETECT_PORT="GPIO_0"

CONFIG_BOOT_USB_DFU_DETECT_PIN=23

CONFIG_BOOT_SERIAL_DETECT_PIN_VAL=0

CONFIG_SINGLE_APPLICATION_SLOT=y

CONFIG_BOOT_SIGNATURE_TYPE_NONE=y

CONFIG_BOOT_SIGNATURE_KEY_FILE="root-ec-p256.pem"

CONFIG_USB_COMPOSITE_DEVICE=n

CONFIG_USB_DEVICE_PID=0x0101

CONFIG_USB_DEVICE_DFU_PID=0x0102

##CONFIG_SIZE_OPTIMIZATIONS=y

# Enable MCUboot Serial Recovery

CONFIG_MCUBOOT_SERIAL=y

##CONFIG_UART_CONSOLE=n

# Point Serial Recovery to CDC_ACM

CONFIG_BOOT_SERIAL_CDC_ACM=y

I have tried with and without specifying the PID.

I am doing the right things here? 
Is the fact that a cdc serial port is open mean that serial recovery is possible and I am using the wrong approach with nrfutil?

Any help appreciated. 

Thanks

[Amanda Hsieh]

Hi, 

Try to add the following configs into child_image/mcuboot.conf:

CONFIG_USB_DEVICE_VID=0x1915
CONFIG_USB_DEVICE_PID=0x5300

Regards,
Amanda H.

[JustinL]

Hi,

Thanks for the quick response.

I have just tried this and the result is the same. Device manager reports "The drivers for this device are not installed. (Code 28)"

I have also checked the device properties and confirmed the VID and PID were picked up correctly.

Looking at the usb compatible ids property device manager reports:

USB\COMPAT_VID_1915&Class_fe&SubClass_01&Prot_01
USB\COMPAT_VID_1915&Class_fe&SubClass_01
USB\COMPAT_VID_1915&Class_fe
USB\Class_fe&SubClass_01&Prot_01
USB\Class_fe&SubClass_01
USB\Class_fe

If that helps. 

 Thanks,

Justin

[JustinL]

Hi Amanda,

Thanks for this.

To clarify - the cdc com port is correctly recognised. However, windows device manager is also reporting a failed usb device mcuboot which has no driver. I am guessing mcuboot is trying to register as a composite device.

I can do firmware updates over the com port using mcumgr but I can't seem to do anything via nrfutil. I believe this is because there is no mcuboot trait because of the failed device.

I was hoping nrfutil would be faster as it takes well over 2 minutes for 150k firmware update via the cdc port.

Also I seem to have to install go in order to use the mcumgr cli and I would rather be using nrfutil.

Thanks,
Justin

[Amanda Hsieh]

Hi,

JustinL said:

However, windows device manager is also reporting a failed usb device mcuboot which has no driver. I am guessing mcuboot is trying to register as a composite device.

Yes, it did, but I don't install any special driver for that. Seems Windows 10 handles that. 

JustinL said:

I believe this is because there is no mcuboot trait because of the failed device.

I agree. 

JustinL said:

Also I seem to have to install go in order to use the mcumgr cli and I would rather be using nrfutil.

Is it possible to try on a Windows 10 pc?

-Amanda H.

[JustinL]

Unfortunately it is not easy for us to try this on a  windows 10 machine.

[Amanda Hsieh]

Hi, 

The team suggest installing nRF Connect for Desktop which would install the drivers for Nordic devices at the same time. Please let me know whether this can help or not. Thanks. 

-Amanda H.

[JustinL]

Hi Amanda,

I already had nRF Connect for Desktop installed. But I updated it to the latest version just to check.

Same result. I just don't think there is a usb dfu device class driver on the system.

So then I followed the advice in this support thread https://devzone.nordicsemi.com/f/nordic-q-a/77824/usb-dfu-class  

and installed winusb. 

And now nrfutil can see the mcuboot trait 

E60EF9D290C74E49
ports COM19
traits mcuBoot, nordicUsb, serialPorts, usb

and I just tried a firmware update and it worked!! I am guessing that if winusb is installed on the system already then this will work. But that is not a standard windows configuration.

I do think that a note in the sample or the build script mentioning this for windows would save a lot of trouble.

Thank you for all your help though,

Justin

[Amanda Hsieh]

Happy to know you fix the issue. 

-Amanda H.