Muhammad Awais Arshad

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

7 years ago.  This question has been closed. Reason: Opinion based - no single answer

Can mbed serial driver support dual CDC VCP device?

I have updated DAPLINK to create two virtual COM ports on a single device. The mbed serial driver could not be installed for second COM port. I have updated oem48.inf (mbed serial driver information file) but that didn't solve the issue.

Any suggestion?

More details can be checked at: https://github.com/mbedmicro/DAPLink/issues/262

Changes done in oem48.inf

[_Devices.ntamd64] %S_DeviceDesc1%=Install,USB\VID_0D28&PID_0203&MI_01, USB\VID_0D28&PID_0203&MI_03 (<< 2nd COM port) %S_DeviceDesc1%=Install,USB\VID_0D28&PID_0204&MI_01, USB\VID_0D28&PID_0204&MI_03

+++++++++++++++++ Device Information ++++++++++++++++++ Device Description : mbed Composite Device Device Path : \.\usb#vid_0d28&pid_0204#06700000066fff525750877267064158a5a5a5a597969906#{a5dcbf10-6530-11d2-901f-00c04fb951ed} Device ID : USB\VID_0D28&PID_0204\06700000066FFF525750877267064158A5A5A5A597969906 Hardware IDs : USB\VID_0D28&PID_0204&REV_0100 USB\VID_0D28&PID_0204 Driver KeyName : {36fc9e60-c465-11cf-8056-444553540000}\0064 (GUID_DEVCLASS_USB) Driver : C:\Windows\system32\DRIVERS\mbedComposite_x64.sys (Version: 1.11.0.0 Date: 2009-09-30) Driver Inf : C:\Windows\inf\oem47.inf Legacy BusType : PNPBus Class : USB Class GUID : {36fc9e60-c465-11cf-8056-444553540000} (GUID_DEVCLASS_USB) Interface GUID : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE) Service : mbedComposite Enumerator : USB Location Info : Port_#0004.Hub_#0003 Container ID : {1f580a63-03af-57a9-8fbb-3ba95eb2c894} Manufacturer Info : mbed Capabilities : 0x94 (Removable, UniqueID, SurpriseRemovalOK) Status : 0x0180600A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER) Problem Code : 0 Address : 4 Power State : D0 (supported: D0, D3, wake from D0) Child Device 1 : mbed Serial Port Device ID : USB\VID_0D28&PID_0204&MI_01\06700000066FFF525750877267064158A5A5A5A597969906 Class : Ports COM-Port : COM31 (\Device\thcdcacm0) Child Device 2 : USB Input Device Device ID : USB\VID_0D28&PID_0204&MI_05\06700000066FFF525750877267064158A5A5A5A597969906 Class : HIDClass Child Device 1 : HID-compliant device Device ID : HID\VID_0D28&PID_0204&MI_05\8&14668A70&1&0000 Class : HIDClass Child Device 3 : mbed Serial Port2 Device ID : USB\VID_0D28&PID_0204&MI_03\06700000066FFF525750877267064158A5A5A5A597969906 Problem : 28 (CM_PROB_FAILED_INSTALL) Child Device 4 : USB Mass Storage Device Device ID : USB\VID_0D28&PID_0204&MI_00\06700000066FFF525750877267064158A5A5A5A597969906 Class : USB Child Device 1 : Disk drive (Disk1) Device ID : USBSTOR\DISK&VEN_MBED&PROD_VFS&REV_0.1\06700000066FFF525750877267064158A5A5A5A597969906&0 Class : DiskDrive Volume : \?\Volume{f81c26c3-1510-11e7-9dcb-b8ca3a81dc59} Kernel Name : \Device\HarddiskVolume89 Mountpoint : F:\

Issue is resolved by adding 2nd vcom port info in mbedSerial_x64.inf and manually forcing windows in device manager to update drivers. Closing.

posted by Muhammad Awais Arshad 27 Jul 2017