Share via

USB-IF Test Certification ID Check

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Type: Automated Test

Overview

This test provides two options to validate USB-IF testing. If the device under test has been certified by the USB-IF, the Test Certification ID is sufficient to fulfill the USB-IF testing requirement. If the USB-IF tests have been downloaded from the USB-IF website at usb.org, a passing test log must be provided to validate completion of the test suite. For more information on how to fulfill the USB-IF testing requirement, visit the following Microsoft Web sitehttps://www.microsoft.com/whdc/connect/usb/WLK_USB-IF_CertReq.mspx

Details

Option 1: USB-IF Test Certification ID

Use this option if the device under test is USB-IF Certified. The test collects the USB-IF test ID (TID) from the user at the time of scheduling the test as part of the editable parameters.

To enter the USB-IF TID, follow these steps:

  1. In the Device Console, select USB-IF Test Certification ID Check from the Available Jobs list.

  2. Right-click the job and select Edit Parameters.

  3. Enter the Test ID, set INTEROP_TESTS_PASSED to TRUE, and then click OK.

  4. Schedule the job normally.

    This test ID will now be applied each time the test is scheduled for the submission.

Option 2: USB-IF Self-Testing

Use this option if the device is not USB-IF Certified.

  1. Download the most current version of the applicable USBCV test suite from the USB-IF’s website.

    For USB 2.0 devices, use the USB20CV tool available for download at https://www.usb.org/developers/tools/.

    For USB 3.0 devices, use the USB30CV tool available for download at https://www.usb.org/developers/ssusb/ssusbtools/.

  2. Install the tool kit and execute the applicable Chapter 9 tests on the device under test.

    Note  The term “Chapter 9” refers to the USB-IF tests, which are based on requirements derived from Chapter 9 of the USB specification.

    Note  Testing can be accomplished on any Windows 7 test system, and the results are valid for non-Windows 7 logo submissions.

  3. Run the appropriate interoperability tests for the device, as described in the WLK USB-IF Testing documentation available at https://www.microsoft.com/whdc/connect/usb/wlk-usb-if-testing.mspx.

  4. Locate the Chapter 9 test log on the test system.

  5. Copy the log file to the DTM client machine, if it is not the same as the test system.

  6. Create a folder on the DTM client called C:\usblogs and place the log file in that folder.

    Note  This is the default location the test will search for log files. The log may be placed anywhere on the system, but the PATH_TO_LOGS parameter must be updated to reflect the location of the log files.

  7. The WLK test will parse through the logs to determine whether the CV tests have passed or failed.

  8. For the interoperability testing, set the INTEROP_TESTS_PASSED parameter to “TRUE” if the Interop test was successful. Otherwise, keep the default value of “FALSE.”

  9. Schedule the job normally. The test will collect and parse the test logs from the client machine.

Run Time: 1 minute

Log File: Usbifvalidation.xml

System Restart Required: No

Test Category: USB_Connectivity

Supported operating systems for Logo or Signature testing:

  • Windows 7

  • Windows Server 2008 R2

  • Windows Vista

  • Windows Server 2008

Program: USBValidation.exe

Requirements

Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above)

  • Software components included with the device that is being tested

Hardware Requirements

The test tool requires the following hardware:

  • Device to be tested

  • Computer that meets the minimum software requirements

  • Windows keyboard

Other Requirements

Completion of this test requires USB-IF certification via test lab or downloading and running USB-IF testing, available from usb.org. Requirements and procedures for USB-IF testing and certification are not documented here.

Processor

The test tool runs on the following processor architectures:

  • x86

  • x64

Command Syntax

Command option Description

USBIFValidation.exe

Without any options, the test will fail.

-d [VID]/[PID]

Use VID/PID combination if running this test for a device.

-I [TESTID]

0
-interop [INTEROP_TESTS_PASSED] FALSE
-f [PATH_TO_LOGS] C:\usblogs

 

Code Tour

File Manifest

File Location

USBValidation.exe

[WTT\TestBinRoot]\nttest\driverstest\usb\logokit

 

 

 

Build date: 9/14/2012