ID | Updated | Subject | Reason | Mandate | Effective Date |
---|---|---|---|---|---|
155 | February, 2023 | Deprecation of EHCI Testing. USB2CV and EHCI Interoperability Optional | Market Adoption of xHCI | Informational | February, 2023 |
|
|||||
137 | May, 2021 | USB2CV only Required on UVC Capable Products. | Products that fail USB2CV fail USB3CV as well. | Required | May, 2021 |
|
|||||
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.
|
||||
![]() |
||||
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.
|
||||
![]() |
||||
USB2CV only Required on UVC Capable Products. Mandate: Required Effective Date: May, 2021 Effective immidiatly all product not implementing UVC are not required to be tested against USB2CV. USB3CV is still required for all products.
|
||||
![]() |
||||
Deprecation of EHCI Testing. USB2CV and EHCI Interoperability Optional Mandate: Informational Effective Date: February, 2023 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. |
||||
![]() |
||||
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. |
||||
![]() |
||||
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.
|
||||
![]() |
||||
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:
There are four possible causes of the failure:
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. |
||||
![]() |
||||
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. |
||||
![]() |
||||
PHDC error "Verify Get Data Status Request Test" Mandate: Informational Effective Date: June, 2009 Failure output:
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:
The PHDC test suite needs to be updated to account for all valid ISO/IEEE Std 11073-20601 message types
|
||||
![]() |
||||
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. |
||||
![]() |
||||
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.
To restore the original Windows EHCI driver, uninstall the Intel Test Stack driver and rescan for hardware changes. |
||||
![]() |
Site sponsored by USB Implementers Forum, Inc., creators of USB technology. |
![]() |
About Us | Privacy Statement |