a USB driver problem

the “Unclassfied” style of DTM test.
The failure item is PNP.

I mean which specific tests were failing, not the specific hw

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Thursday, August 20, 2009 11:33 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] a USB driver problem

The DTM version is 1.1.
My device is a ZTE CDMA handset which adopts MS’s CDC driver.
When I used DTM to do WHQL test, I found there were several items failed, such
as PNP test.

Can you be a little more specific?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Thursday, August 20, 2009 9:59 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] a USB driver problem

I have ever used usbser.sys under XP system to do dtm test and found that some
items failed.
such as pnp test item etc.

Which dtm test failed in usbser?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: xxxxx@hotmail.com
Sent: Thursday, August 20, 2009 7:07 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] a USB driver problem

thanks everyone.

The usbser.sys can not pass DTM test.
So, My device can’t adopt usbser.sys and I must write the driver by myself.

my problem is as follows:
How to design my driver which can support both Modem and COM device for
different USB interface?

thanks a lot.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Thanks to Doron and Tim ,

As for "You do not need a bus driver, usbccgp can be used to split the 2 interface functions apart in separate child stacks. You should use the in box driver usbser.sys for the modem function and then have your own driver for the com port. These will installed qwith two different INFs since modems are in a different device class (Modem) than com ports (Ports) " ,

I partly agrees .

I wanna know that ,

what scenario is a customized ccgp driver needed ?

Please help take an example that MS CCGP can’t fully support and we need customized a new ccgp.

Daniel Xie wrote:

what scenario is a customized ccgp driver needed ? Please help
take an example that MS CCGP can’t fully support and we need
customized a new ccgp.

Ah, one of my favorite questions. I feel giddy, like Tim Roberts must feel when he’s about to announce he can do 40MB/sec over a bulk pipe.

Here’s the ones I can think of. Note that this applies for XP and earlier. Some of this has been improved in Vista+:

  1. You are using an inflexible class driver that expects very specific things of the USB interface it (thinks it’s) talking to. example: usbser.sys which expects interfaces 0 (and 1) below it. Note that this can also be solved with a lower filter on the child stack like I proposed earlier.

  2. You need ‘custom’ grouping of USB interfaces into child PDOs. example: usbser.sys again (or really, CDC ACM) because usbccgp doesn’t understand the CDC union descriptor format

  3. You want custom/newish compatible ID’s applied to your child PDOs based on some properties of your device’s individual interface(s). example: we had a composite MTP + debugging interface device, we needed to put the MS_COMP_MTP (or whatever it was) compatible ID on the child PDO so that the WMP11 driver would load on it. Otherwise we just got “USB imaging device” or something.

yongfan yongfan wrote:

The usbser.sys can not pass DTM test. So, My device can’t adopt
usbser.sys and I must write the driver by myself.

I think your claim here is a little broad. The driver itself is fully capable of passing DTM (believe me, I’ve done it).

Have you actually done an investigation to root cause why you can’t pass? You say that PNP test failed, are you sure your device is enumerating properly on USB as it’s stopped and started, etc.?