C-type USB Hardware descriptor fail

Hi,

I have developed a USB MIDI application, in which I have deployed USB Device functionality through USB C-type connector. However, when I test the USB virtual COM Port functionality with window10 PC, it shows an error message " Windows has stopped this device because it has reported problems. (Code 43)". Therefore, what's the problem? Is it from our custom board side or in window?

ERROR:

Device USB\VID_0000&PID_0002\5&2bdbfb1c&2&4 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_2E04&PID_C026\5&2bdbfb1c&0&4
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(HS04)
Migration Rank: 0xF000FFFFFFFF0000
Present: false
Status: 0xC0000719

Kindly suggest the relevant solution for same.

Parents Reply
  • Hi,

    The nRF52840 has a USB interface which consist of VBUS, GND, D+ and D- which is USB 2.0 if I'm not mistaken. If you want to connect this to USB-C then you have to give special attention to the CC1 and CC2 as these pins are used for cable orientation detection, and defines the role of the device. 

    Is the device going to be a USB host(downstream) or a USB device(upstream)? 

    Most likely it will be USB device. 


    If it's going to be a USB device then you typically need to connect a pulldown resistor to both CC1 and CC2 pins. This means that the host will power the device. 

    Letting the CC pins float will result in unpredictable behavior.

    regards

    Jared 

Children
Related