USB-IF Compliance Updates

Number of Updates: 9

Table of Contents
ID Updated Subject Reason Mandate Effective Date
111 April, 2017 Billboard Specification Updated from 1.1 to 1.21 The BCD version for the Billboard specification was updated. Required April, 2017

109 March, 2017 TD 10.25 Hub Global Suspend and Unacknowledged Connect Remote Wakeup Announcment of an update to hub requirements Required January, 2017

48 October, 2013 USB20CV Release 1.4.10.2 Announcement of an Update to USB20CV Required October, 2013

33 July, 2011 USB20CV is Unable to Initialize and Execute Tests. "Could not select Test Stack" error message Informational Now

68 May, 2011 Additional USB 3.0 Compliance Requirement for USB 2.0 Based Certified Products Ensures Interoperability between USB 2.0 and USB 3.0 Required January, 2010

71 January, 2011 64-bit USB20CV is Unable to Initialize and Execute Tests. "Could not select Test Stack" error message Informational September, 2010

65 June, 2009 PHDC error "Verify Get Data Status Request Test" Unsupported ISO/IEEE Std 11073-20601 Message Types Informational June, 2009

20 February, 2007 USBCV requires hubs to support port power switching Clarification Informational Now

19 February, 2007 High-speed Devices must have USBCV tests performed at both HS and FS Clarification Required Now

TD 10.25 Hub Global Suspend and Unacknowledged Connect Remote Wakeup
Mandate: Required
Effective Date: January, 2017
Effective immediately USB 2.0 and USB 3.1 hubs must pass  TD 10.25 Hub Global Suspend and Unacknowledged Connect Remote Wakeup in USB command verifier. Documentation on this test can be found in the command verifier documentation downloaded with the tool.
Top
Billboard Specification Updated from 1.1 to 1.21
Mandate: Required
Effective Date: April, 2017
The BCD version of the Billboard Specification was updated. The BCD value requried is now 1.21. USBCV will flag all implementations that do not have a BCD version of 1.21.
Top
High-speed Devices must have USBCV tests performed at both HS and FS
Mandate: Required
Effective Date: Now
For high-speed peripherals, Chapter 9 (device framework) tests must be executed twice: with the USB peripheral running at full-speed and again at high-speed. If the USB peripheral is a hub or compound peripheral, then Chapter 11 must be executed at each speed as well.

It is not necessary to run HID, Mass-Storage (MSC), Video Class (UVC) and OTG tests at both speeds.
Top
USBCV requires hubs to support port power switching
Mandate: Informational
Effective Date: Now
USBCV requires HS hubs to support port power switching on its downstream ports. This is not documented anywhere. Because port power switching is optional, there are some certified HS hubs that do not support it. Port power switching enables the host to turn VBus on or off for downstream ports of hubs on command. Should a certified hub that does not support port power switching be used with USBCV, devices that take too long to connect after VBus is asserted will always pass instead of being marked failed. The hubs used at workshops, and hopefully in your labs, implement port power switching and will fail devices that take too long to connect. Thus, please be sure to use the gold-tree HS hubs when running USBCV.
Top
USB20CV is Unable to Initialize and Execute Tests.
Mandate: Informational
Effective Date: Now

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.

Top
USB20CV Release 1.4.10.2
Mandate: Required
Effective Date: October, 2013

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.

Top
PHDC error "Verify Get Data Status Request Test"
Mandate: Informational
Effective Date: June, 2009

Failure output:

Verify Get Data Status Request Test Failed
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

 

Top
Additional USB 3.0 Compliance Requirement for USB 2.0 Based Certified Products
Mandate: Required
Effective Date: January, 2010
All USB 2.0 peripherals seeking certification are required to demonstrate enumeration on the USB 3.0 PDK. Any failure to enumerate and pass the USB 2.0 Chapter 9 Device Framework tests and applicable class tests in USB30CV will be thoroughly investigated and the company may request a waiver.

The USB30CV tests must be performed at each supported speed of the product. If the product is hi-speed capable, then full-speed tests must be performed as well.
Top
64-bit USB20CV is Unable to Initialize and Execute Tests.
Mandate: Informational
Effective Date: September, 2010

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.

Top

Site sponsored by USB Implementers Forum, Inc., creators of USB technology.
VTM Engineering and Technical Services Group
About Us | Privacy Statement