Win7 DTM

We are working on DTM for USB-VCP driver and currently performed unclassified section (reliability) testing for XP-86 and 64 machines.

However for in Windows 7, the un-classified (device fundamental) section is having an extra set of cases i.e. “Connectivity USB” (apart from the regular Driver-reliability cases)

Are these required/mandatory to get WHQL?

below is the list:
“Connectivity USB” -
USB Address Description Test,
USB Description Test,
USB Device Control Requests,
USB Device Framework (CV),
USB Disable/Enable,
USB Driver Level Re-enumeration test,
USB Enumeration Stress,
USB Isochronous Alternative Interface Presence,
USB Selective suspend,
USB Serial number,
USB Specification Compliance,
USB System Suspend resume and
USB-IF test certification ID Check.

We tried running all these, out of the 13 cases, 8 were not successful.

Do all these cases needs to be passed for getting Virtual USB com port driver WHQL pass?

xxxxx@gmail.com wrote:

We are working on DTM for USB-VCP driver and currently performed unclassified section (reliability) testing for XP-86 and 64 machines.

However for in Windows 7, the un-classified (device fundamental) section is having an extra set of cases i.e. “Connectivity USB” (apart from the regular Driver-reliability cases)

Are these required/mandatory to get WHQL?

Yes. They are also required in order for your device to get certified
as USB-compliant by the USB Implementor’s Forum. If you are failing any
of these tests, then your device’s firmware is not correct.

below is the list:
“Connectivity USB” -
USB Address Description Test,
USB Description Test,
USB Device Control Requests,
USB Device Framework (CV),
USB Disable/Enable,
USB Driver Level Re-enumeration test,
USB Enumeration Stress,
USB Isochronous Alternative Interface Presence,
USB Selective suspend,
USB Serial number,
USB Specification Compliance,
USB System Suspend resume and
USB-IF test certification ID Check.

We tried running all these, out of the 13 cases, 8 were not successful.

Do all these cases needs to be passed for getting Virtual USB com port driver WHQL pass?

With one exception, yes. If you have real hardware, then it’s not
really a “virtual” com port. It’s a USB communication device. Right?

The exception is the “USB-IF test certification ID check”. When the
latest DTM came out, Microsoft added a requirement that you send your
hardware to an independent laboratory to get certified (on these tests,
by the way). That lab would give you a certification number. You were
then required to enter the certification number as one of the parameters
of this test. That requirement has since been dropped, and when you
apply the exceptions, that one failure will not be counted against you.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Are these test cases meant for the Windows-driver or the USB-device?

Not fully sure, as these devices fall in Communication device category

Below is the USBVIEW o/p for analysis:

=========================================
Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bcdDevice: 0x0100
iSerialNumber: 0x03
bNumConfigurations: 0x01

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x01

Configuration Descriptor:
wTotalLength: 0x0043
bNumInterfaces: 0x02
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 (Bus Powered )
MaxPower: 0x19 (50 mA)

Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x00

Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x00

=========================================

Also internally these devices are not obeying standard commands for CDC.

xxxxx@gmail.com wrote:

Are these test cases meant for the Windows-driver or the USB-device?

Both, really. DTM tests your “device”. That encompasses the hardware,
the driver, and some of the supporting software. For a USB device, that
means passing the USB compliance tests.

Not fully sure, as these devices fall in Communication device category

Have you checked the DTM results to get the exact error messages for the
failures? That’s where you need to be looking.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.