views:

211

answers:

1

Hi All,

I bought a USB to Serial cable which claims to be CDC compliant.

But the bInterfaceClass value in interface descriptor is 0xFF(which is vendor specific). I was expecting it to be 0x02 (Communications and CDC control).

In the device manager, i found that the drivers being loaded are ser2pl.sys and serenum.sys. I had learnt usbser.sys is the windows CDC driver, but it was not loaded for my cable.

I am pretty much new to this CDC, so i have following questions

1.Does this indicate that the cable is not CDC compliant 2.Can i make this cable CDC compliant (since CDC is a driver functionality), by loading usbser.sys. If yes how?

A: 
  1. I don't know for sure but thats indication that cable will not necessary follow CDC
  2. I don't think you can make it compliant but if you want to use usbser.sys as driver for that cable you should provide inf file which should load usbser.sys if your cable is connected, check the driver VID PID etc probably this should help http://www.mjmwired.net/kernel/Documentation/usb/gadget_serial.txt (search for usbser.sys and look for .inf file, and modyfi it accordingly.
CrazyChris
Thanks for the information.I had tried this earlier, but the driver setup was failing in the end , saying device cannot start (error code 10).
Harsha
It is difficult for me to diagnose but i think it means that usbser.sys fails to create service to handle virtual com. It can be because of many reasons, maybe wrong configuration was send by yours cable or more likely usbser.sys don't supports your's cable configration. Btw can give more info about that cable ?
CrazyChris