Prev: SDIO development
Next: Compile error after adding #define WPP_GLOBALLOGGER
From: Bo Skjoett on 30 Nov 2009 07:57
I don't know if this is the right forum to ask technical questions regarding
tests in the Windows Logo Kit (WLK) and DTM Studio, but I haven't found a
better place to post.

My problem is that my Unclassified Signature device driver test fails for my
USB device driver. The failing test is called "USB Device Framework (CV)".
The failing test case is called "Reset External Hub Port". I suspect the
error occurs because the USB hub is a USB 1.1 compliant hub, but not USB 2.0
compliant. My device has an internal USB hub which I cannot replace with a
USB 2.0 complaint hub.

Am I right that the "USB Device Framework (CV)" test requires a USB 2.0
compliant hub?

From: Tim Roberts on 30 Nov 2009 23:56
Bo Skjoett <BoSkjoett(a)discussions.microsoft.com> wrote:
>
>My problem is that my Unclassified Signature device driver test fails for my
>USB device driver. The failing test is called "USB Device Framework (CV)".
>The failing test case is called "Reset External Hub Port". I suspect the
>error occurs because the USB hub is a USB 1.1 compliant hub, but not USB 2.0
>compliant. My device has an internal USB hub which I cannot replace with a
>USB 2.0 complaint hub.
>
>Am I right that the "USB Device Framework (CV)" test requires a USB 2.0
>compliant hub?

No, but if you are USB 1.1, then your hub must be strictly 1.1 compliant.
Does your hub support reset correctly? Have you run the USB-IF compliance
tests?
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Bo Skjoett on 1 Dec 2009 08:11
I just read the description of the "USB Device Framework (CV)" test on MSDN
(http://msdn.microsoft.com/en-us/library/dd450466.aspx) and it says:

<quote>
This test verifies that the test device supports the commands set forth in
Chapter 9, “USB Device Framework” of the Universal Serial Bus (USB)
Specification Revision 2.0. It verifies that the test device responds
correctly to device, configuration, and interface descriptor requests.

This test requires the test device to be connected through an intermediate
USB 2.0 hub to the host system.
</quote>

This sounds like a strict USB 2.0 requirement. My problem is that our device
has a built-in USB 1.1 hub that I cannot by-pass. The USB device that my
device driver is targeting is connected to the internal hub.

So what can I do? Any advice is appreciated.


"Tim Roberts" wrote:

> Bo Skjoett <BoSkjoett(a)discussions.microsoft.com> wrote:
> >
> >My problem is that my Unclassified Signature device driver test fails for my
> >USB device driver. The failing test is called "USB Device Framework (CV)".
> >The failing test case is called "Reset External Hub Port". I suspect the
> >error occurs because the USB hub is a USB 1.1 compliant hub, but not USB 2.0
> >compliant. My device has an internal USB hub which I cannot replace with a
> >USB 2.0 complaint hub.
> >
> >Am I right that the "USB Device Framework (CV)" test requires a USB 2.0
> >compliant hub?
>
> No, but if you are USB 1.1, then your hub must be strictly 1.1 compliant.
> Does your hub support reset correctly? Have you run the USB-IF compliance
> tests?
> --
> Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.
> .
>
From: Tim Roberts on 2 Dec 2009 23:19
Bo Skjoett <BoSkjoett(a)discussions.microsoft.com> wrote:
>
>I just read the description of the "USB Device Framework (CV)" test on MSDN
>(http://msdn.microsoft.com/en-us/library/dd450466.aspx) and it says:
>
><quote>
>This test verifies that the test device supports the commands set forth in
>Chapter 9, �USB Device Framework� of the Universal Serial Bus (USB)
>Specification Revision 2.0. It verifies that the test device responds
>correctly to device, configuration, and interface descriptor requests.
>
>This test requires the test device to be connected through an intermediate
>USB 2.0 hub to the host system.
></quote>
>
>This sounds like a strict USB 2.0 requirement. My problem is that our device
>has a built-in USB 1.1 hub that I cannot by-pass. The USB device that my
>device driver is targeting is connected to the internal hub.
>
>So what can I do? Any advice is appreciated.

It appears that your only choice is to apply to Winqual for an exception to
the rule. However, if their logo requirements include USB 2.0 hub, then
you will not be able to get a signature for your device.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
 | 
Pages: 1
Prev: SDIO development
Next: Compile error after adding #define WPP_GLOBALLOGGER