USB-CAN adapter doesn't work in new pc

[ZioGianni]

I have bought USB-CAN adapter based on STM32F042C6 microcontroller with open source code:

https://github.com/candle-usb/candleLight_fw/tree/master

With very new pc adapter doesn't work, windows doesn't recognize driver, with old pc windows use automatically winusb.sys.

If i install manually winusb using Zadig i see in Device manager that device is recognized but i cannot communicate with him.

I try to many pc and seems that the problem is related to host controller, in new PCs with host controller 3.1 extensible doesn't work, in PCs where it is also EHCI the device work.

Someone have some similar problem?

XHCI must be compatible with old device so I think that there is some error in firmware.

 

Thanks for help

Gianni

[Pavel A.]

On the new PC, is secure boot enabled?

 

To install manually, you don't even need zadig. Just install the winusb driver from device manager.

> seems that the problem is related to host controller

Then try to plug the device thru a good USB 2.0 hub.

 

[ZioGianni]

Thank you Pavel for your answer.

I did a try also with secure boot disabled and with USB 2.0 hub but nothing change.

Attached USB descriptor dumping.

[Andrew Neil]

---

@ZioGianni wrote:

I have bought USB-CAN adapter based on STM32F042C6 microcontroller with open source code:

https://github.com/candle-usb/candleLight_fw/tree/master

With very new pc adapter doesn't work

---

So have you raised an issue with the project:

https://github.com/candle-usb/candleLight_fw/issues

 

How about this one:

https://github.com/candle-usb/candleLight_fw/issues/20

 

[ZioGianni]

The issue #20 seems to be similar but i don't understand how to try, maybe i need a F4devboard to do the same test.

To me seems that the problem is that:

0xE0 0x0409 Request failed with 0x0000001F

 

In the firmware i see that 0xE0 is defined and used and i don't understand why doesn't work only on very new PC with all 3.x USB ports.

Is there a way to ask to Microsoft to ignore the string descriptor?

Maybe modifying win register?

[Pavel A.]

Aha this is a composite device with two interfaces. When you install the driver manually, make sure that winusb is installed on the 1st interface (custom), not on the main device (the parent of two interfaces).

 

[ZioGianni]

Yes, it is a composite device because there is also DFU interface.

I have installed driver manually on both interaces of composite device and not in the main device but nothing changed.

[Pavel A.]

Well if the winusb driver successfully installs on the device (no errors appear in eventlog and device manager) it looks like a software problem. A USB bus analyzer can help to understand is this a hardware or software problem. Whoever sells this device should be informed.