Effective immidiatly all product not implementing UVC are not required to be tested against USB2CV. USB3CV is still required for all products.

To reflect the markets adoption of xHCI host controllers the USB-IF compliance program will no longer enforce testing on EHCI host controllers. This includes the previously required test Categories of USB2CV and EHCI Interoperability.

The following error message may occur when attempting to execute USB20CV on Windows XP or Windows 7:

InitializeTestSuite

INFO Microsoft Windows XP (Build 2600) INFO Service Pack 2.0 INFO USBCommandVerifier.dll ver 1.3.0.3 INFO TestServices.dll ver 1.3.0.3 INFO StackSwitcher.dll ver 1.3.0.3 ERROR Could not select Test Stack INFO Summary Log Counts [ Fails (0); Aborts (0); Warnings (0) ]

There are four possible causes of the failure:

1. Do not have a mass storage device connected to USB at the time USB20CV is initially loaded. This can prevent switching out the Microsoft EHCI driver with the USBCV diagnostic driver.
    
2. Verify that the "Target" defined in the Windows shortcut to USBCV looks similar to the following:
   "C:\Program Files\USB-IF Test Suite\USB20CV\USB20CV.exe" /title "USB 2.0 Command Verifier" /drv hcdriver
   
   Also, the default directory (called "Start in:" in the Windows shortcut) should point to the "lib" directory of USBCV.
   "C:\Program Files\USB-IF Test Suite\USB20CV\lib\"
    
3. USB20CV can only run on the English language version of Microsoft Windows XP and Microsoft Vista.  USBCV is not unicode compliant.
    
4. USB20CV requires an EHCI compliant host controller. A high-speed hub is required between the root port and the device being tested.

Windows 2008 Server requires drivers to be signed.  The Test Stack is not a signed driver.  To load the Test Stack, reboot the system and use the F8 key to show the boot menu.  From the menu, select the option that allows unsigned drivers to be loaded.

A update to the device framework tests is available.  USB20CV, Release 1.4.10.2 is available for download from the USB-IF tools webpage. 

Please see the Release Notes that is included in with the installation of the tool for information regarding this revision.

Failure output:

INFO    Now Starting Test:  Valid Get Data Request data Test (Configuration Index 0)
ERROR   Failed to get the 11073 message type, interface num 0x0
FAIL    11073 DLL API failure.
INFO    Re-enumerating PHDC device
INFO    Stopping Test [  Valid Get Data Request data Test (Configuration Index 0):
     Number of: Fails (1); Aborts (0); Warnings (0) ]

This output indicates that the peripheral responded to the GetDataStatus request correctly; however, the data read from the active bulk endpoint did not match a supported ISO/IEEE Std 11073-20601 message types (For example, a scan report.).  The types of messages that the PHDC test supports are: 

• Association Request/Response
• Release Request/Response
• Abort
• MDS Response
• Event Report with measurement data 

The PHDC test suite needs to be updated to account for all valid ISO/IEEE Std 11073-20601 message types

I minor detail was left out of the "USBCommandVerifier_Release_Notes__64bit." In the 32-bit USB20CV, the EHCI driver is automatically swapped out with a proprietary EHCI test driver. This feature is not available in the 64-bit version (at this time). So you will need to manually replace the Windows EHCI driver with the test EHCI driver.

1. Within Device Manager, locate the Enhanced Host Controller located under the Universal Serial Bus controllers
2. Right click and Update the Driver Software
3. Select "Browse the Computer for Driver Software"
4. Select "Pick from a List of Device Drivers"
5. Make sure the "Show compatible hardware" is checked
6. Select the "Intel® USB 2.0 Enhanced Host Controller" then choose "Have Disk"
7. Browse to C:\Program Files\USB-IF Test Suite\USB20CV\TestStackDriver (or something similar) and locate the hcdriver.sys file. At this point, the "Intel EHCI Compliance Test Tool" should be displayed in the hardware model window.  Select it and choose "Next."
8. Windows Security will issue a warning.  Install the driver anyway.
9. The Windows EHCI stack should now be replaced by the "Intel EHCI Compliance Test Tool" driver the next time the PC is booted.
10. Reboot the system.  The "Intel EHCI Compliance Test Tool" driver is not signed and Windows will not automatically load an unsigned driver.  Prior to Windows loading, press F8 and disable driver signature enforcement in order to load the unsigned driver.

To restore the original Windows EHCI driver, uninstall the Intel Test Stack driver and rescan for hardware changes.