USB-IF Compliance Updates

Number of Updates: 5

Table of Contents
ID Updated Subject Reason Mandate Effective Date
65 June, 2009 PHDC error "Verify Get Data Status Request Test" Unsupported ISO/IEEE Std 11073-20601 Message Types Informational June, 2009
48 May, 2009 USB20CV Release 1.3.5 Announcement of an Update to USBCV (note the name change) Required May, 2009
33 August, 2007 USBCV is Unable to Initialize and Execute Tests. "Could not select Test Stack" error message Informational Now
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

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
USBCV is Unable to Initialize and Execute Tests.
Mandate: Informational
Effective Date: Now

The following error message may occur when attempting to execute USBCV.

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 USBCV 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\USBCommandVerifier\USBCV13.exe" /title "USB Command Verifier Beta" /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\USBCommandVerifier\lib\"
     
  3. USBCV Release 1.3.1 can only run on the English language version of Microsoft Windows XP and Microsoft Vista.  USBCV is not unicode compliant.
     
  4. USBCV requires an EHCI compliant host controller. A high-speed hub is required between the root port and the device being tested.
Top
USB20CV Release 1.3.5
Mandate: Required
Effective Date: May, 2009

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

This revision has a new name: USB20CV (formerly USBCV).  The name change is in preparation for a separate USB 3.0 version.

USB20CV, Release 1.3.5, includes tests for the new Personal Healthcare Device Class (PHDC).
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

Site sponsored by USB Implementers Forum, Inc., creators of USB technology. VTM Association Management
About Us | Privacy Statement