none
WLK 1.6 Configuration Problem for USB_CONNECTIVITY for Win7 RRS feed

  • Question

  • I am trying to pass my driver for a USB3.0 device through WLK suite.

    While the Driver Reliability tests succeed several test of the Connectivity_USB part are failing.

    USB Address Description test
    USB Descriptor Test
    [...]

    Is a specific setup required for these tests?

    Currently I have my device directly attached to a pci-express usb3.0 adapter card.

    Thanks

    Tuesday, October 30, 2012 10:25 PM

Answers

  • I've found this page on the "Execute USB Device Framework (CV)" test.  http://msdn.microsoft.com/en-us/library/ff568586(VS.85).aspx

    It appears that the device being tested must be connected to a USB hub which is connected to the test system.  While other controllers have been disabled.

    From the linked page the setup is described as:

    Setup

    This test requires the test device to be connected through an intermediate USB 2.0 hub to the host system. If the test machine has two USB controllers, disable the controller that is not under test (or else the test fails).


    Paul - This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, November 1, 2012 8:07 PM

All replies

  • These are the instructions from the HCK documentation for these tests.  While they may not be exactly the same, they should not have changed much, so may be of help.

       USB Address Description test: http://msdn.microsoft.com/en-us/library/windows/hardware/jj124277.aspx

       USB Descriptor Test: http://msdn.microsoft.com/en-us/library/windows/hardware/hh998147.aspx

    By reading through these, I found a link to:

       USB Device.Connectivity Testing Prerequisites: http://msdn.microsoft.com/en-us/library/windows/hardware/hh998730.aspx

    This describes the testing requirements for the USB tests.


    Paul - This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, October 31, 2012 7:34 PM
  • Thanks a lot for your reply.

    Meanwhile I succeeded running USB Address Description Test and USB Descriptor Test. The key point was to use a EHCI host controller instead of the xHCI host controller.

    Now all but one test are running.  The remaining test is "Execute USB Device Framework (CV)". which fails with following text:

    Error 11.1.2012 10:48:36.856 Intialization - A device was not found. Please make sure that you have one plugged in.
    File: d:\6229t\testsrc\driverstest\usb\compliancetools\usbcheck\usbcommandverifier\source\commonhelperfunctions.cpp Line: 262
    Error Type: BOOL
    Error Code: 0x0
    Error Text: Error 0x00000000
    Error 11.1.2012 10:48:36.856 If you are testing a full/low speed device, please connect the device to a USB 2.0 high speed hub and connect the USB 2.0 high speed hub to the USB 2.0 host controller on this system.
    File: d:\6229t\testsrc\driverstest\usb\compliancetools\usbcheck\usbcommandverifier\source\commonhelperfunctions.cpp Line: 272
    Error Type: BOOL
    Error Code: 0x0
    Error Text: Error 0x00000000

    Any ideas how this one has to be setup?

    Thanks, G.

    Thursday, November 1, 2012 3:55 PM
  • I've found this page on the "Execute USB Device Framework (CV)" test.  http://msdn.microsoft.com/en-us/library/ff568586(VS.85).aspx

    It appears that the device being tested must be connected to a USB hub which is connected to the test system.  While other controllers have been disabled.

    From the linked page the setup is described as:

    Setup

    This test requires the test device to be connected through an intermediate USB 2.0 hub to the host system. If the test machine has two USB controllers, disable the controller that is not under test (or else the test fails).


    Paul - This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, November 1, 2012 8:07 PM
  • Great, that was exactly what I needed to know.

    Thanks, G.

    Friday, November 2, 2012 9:21 AM