xHCI Interoperability Test Procedures For Peripherals, Hubs,Host

xHCI Interoperability Test Procedures For Peripherals, Hubs,Host
USB Implementers Forum
xHCI Interoperability Test Procedures For
Peripherals,
Hubs,
Hosts
Revision 1.6 – February 2015
Intellectual Property Disclaimer
THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES
WHATSOEVER INCLUDING ANY WARRANTY OF MERCHANTABILITY,
FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY
OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR
SAMPLE.
A COPYRIGHT LICENSE IS HEREBY GRANTED TO REPRODUCE AND
DISTRIBUTE THIS DOCUMENT FOR INTERNAL USE ONLY. NO OTHER
LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY
OTHER INTELLECTUAL PROPERTY RIGHTS IS GRANTED OR INTENDED
HEREBY.
INTEL CORPORATION AND THE AUTHORS OF THIS DOCUMENT DISCLAIM
ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF
PROPRIETARY RIGHTS, RELATING TO IMPLEMENTATION OF
INFORMATION IN THIS DOCUMENT. INTEL CORPORATION AND THE
AUTHORS OF THIS DOCUMENT ALSO DO NOT WARRANT OR
REPRESENT THAT SUCH IMPLEMENTATION(S) WILL NOT INFRINGE
SUCH RIGHTS.
ALL SUGGESTIONS OR FEEDBACK RELATED TO THIS DOCUMENT
BECOME THE PROPERTY OF INTEL CORPORATION UPON SUBMISSION.
INTEL CORPORATION MAY MAKE CHANGES TO THIS DOCUMENT,
SPECIFICATIONS, PRODUCT DESCRIPTIONS, AND PLANS AT ANY TIME,
WITHOUT NOTICE.
Notice: Implementations developed using the information provided in this
document may infringe the patent rights of various parties including the parties
involved in the development of this document. No license, express or implied, by
estoppel or otherwise, to any intellectual property rights (including without
limitation rights under any party’s patents) are granted herein.
This document is an intermediate draft for comment only and is subject to
change without notice. Readers should not design products based solely on
these documents but should use the USB IF specifications available through the
USB IF. The specifications available through the USB IF have the final authority
in any and all cases where a conflict or difference between this specification and
the specifications seem to occur.
All product and specification names are trademarks, registered trademarks, or
service marks of their respective owners.
Copyright © 2014 Intel Corporation. All rights reserved.
SUMMARY OF CHANGES
Revision:
1.2 – 1.4
1.5
Author:
Sydney Fernandes
et al.
Martin Franke
Section:
2.1
Change:
Rearranged operation of microphone. Added
Device Speed verification.
2.3
Please read entire section
3.1
Rearranged operation of microphone. Added
Device Speed verification.
3.3
Please read entire section
5.2
Rearranged operation of microphone. Added
Device Speed verification.
5.3
Please read entire section
Chapter 7
Added Device Speed Verification. Turn off/on
external power during cold boot
Appendix A
2.4
Please read entire section
Peripheral LPM Test Steps
All
Re-organized document to have chapters and
relabeled figures.
Updated Peripheral Current Measurement Tests
2.2
3.3
1.51
Martin Franke
3.4
Added section for Hub Current Measurement
Tests
Added section for Hub L1 Tests
3.5.2
Edited Hub L1 Test device attachment order
5.4
Added Host L1 Tests
Removed FS Keyboard hubs and the Self-Power
Hubs underneath changing to Self-Power FS
Hubs only.
Added display adapter to all trees
Removed one SS mass storage device and printer
from trees.
Added Windows 8 Support
Removed Active Detach/Attach test
Reviewed entire document and made changes at
various sections in the document
Update OS software requirements for Peripheral,
Host and Hub Testing.
Added Host and Peripheral interim tree. Note
that 5 SS hubs are required for testing.
1.52
Martin Franke
All
1.53
Martin Franke
Sydney Fernandes
All
1.54
Sydney Fernandes
1.2
Appendix B
All
2.1.8
1.55
Sydney Fernandes
Martin Franke
1.56
Sydney Fernandes
1.57
Martin Franke
2
8 Appendix
A
1.2
Appendix B
6 (section 2
and 3)
1.2.1
5.5
7
All
6
1.58
Sydney Fernandes
Sydney Fernandes
1.59
Martin Franke
1.6
Sydney Fernandes
Martin Franke
Jamie Grimm
1.2.2
5.4
8.2
7.1
Appendix B
(Chapter 3)
All
2.2, 3.2 and
6.4
1.2.1
2.2
Removed headset from all trees in the main
document
Removed All Device Tests section (sleeps and
boots) when DUT is behind FS hub at Topology
Change 2
Changed device cable to 3 meter length in
diagrams
Fixed reference minor errors
Changed Figure 8-1 title to reflect only device
Added Mixed Interop. Also added HS Camera
to the tree
Clarified concurrent operation after resume from
Hybrid Sleep and Hibernate
Removed Windows 7
Added Connected Standby Batch Script
Added RTC PowerGates test
Added Connected Standby test to list of steps to
perform
General formatting questions
Added Chapter 6 for testing Compound Devices
Added LPM Test for Host (Hub and U1U2 )
Added Power Capabilities Verification
Updated the Driver Verifier list of files and flag
Added additional test item for Inactive
Detach/reattach for hub downstream port
Added a test for 1 HUT with 2 KGD’s connected
to downstream ports
General Formatting
Specified current measurement at High-speed
Added current measurement graphic
Changed OS from Win 8 to Win 8.1
Updated error in current measurement pass/fail
criteria
1 xHCI Interoperability Testing
xHCI Interoperability testing covers several areas including device framework, demonstrated
operation and the device’s ability to operate and coexist with other USB devices. It also provides
insight into usability issues of the device and the associated software.
xHCI Interoperability testing makes use of an arrangement of USB peripherals known as the
SuperSpeed Interop Tree. The SuperSpeed Interop Tree consists of these characteristics:





Provides isochronous, bulk, interrupt and control traffic
Contains devices behind 5 levels of nested hubs – the maximum allowed
Contains devices more than 15 meters from an xHCI based controller
Contains hubs that operate at SuperSpeed, high-speed and full-speed
Contains devices that operate at SuperSpeed, high-speed, full-speed and low-speed
The xHCI Interoperability test procedure is generic and should be applicable to the vast majority
of devices. This document cannot cover all possible types, configurations and combinations of
peripherals, hubs, hosts and embedded devices. Thus, the application of the xHCI
Interoperability test procedures may need to be modified in order to adequately test a device for
USB compliance. Test guidelines for unique devices that do not fall into categories outlined in
this document should be brought to the attention of TechAdmin@usb.org for assistance.
1.1
Equipment
Note that the equipment listed, the test procedure steps, and the actual list of required tests are
expected to change periodically. Please refer to http://www.usb.org/developers/compliance on the
USB-IF, Inc. Web site for the latest updates to the xHCI Interoperability test procedures.
All references to SuperSpeed hubs in this document are actually USB 3.0 hubs with USB 2.0 and
SuperSpeed functionality.
Item
Description/Model
Qty
USB host system
1. A computer containing an available slot for a Certified USB xHCI controller
or an integrated Certified USB xHCI controller.
2. A multiple core processor is required
1
SS hub(self-powered)
Any Certified SuperSpeed USB 3.0 self-powered hub with at least 4
downstream ports
5
HS hub w/STT (self-powered)
Any Certified USB self-powered, high-speed hub with a single TT and at least 4
downstream ports
1
HS hub w/MTT (self-powered)
Any Certified USB self-powered, high-speed hub with multiple TTs and at least
4 downstream ports
1
HS hub(self-powered)
Any Certified USB self-powered, high-speed hub with at least 4 downstream
ports
1
FS hub (self-powered)
Any Certified USB full-speed hub with at least 2 downstream ports
2
SS low power UASP drive
Any Certified SuperSpeed USB low-power/self-powered mass storage device
compliant with the Mass Storage UASP Class
1
SS video camera
Any Certified SuperSpeed USB video camera compliant with the Video Class
1
FS drive
Any Certified USB high-speed or full-speed mass storage device compliant with
the Mass Storage Class
1
HS drive
Any Certified USB high-speed mass storage device compliant with the Mass
Storage Class
1
FS video camera
Any Certified USB full-speed or high-speed video camera compliant with the
Video Class that can stream video at full-speed
1
Mouse
Any Certified USB low-speed mouse compliant the Human Interface Device
(HID)Class
1
Headset
Any Certified USB headset compliant with the Audio Class that can operate at
full-speed and has both headphones and a microphone
1
Display Adapter
Any Certified USB Display Adapter that can operate at SuperSpeed
1
three meter SS USB cable
Any Certified SuperSpeed USB 3.0 cable assembly
5
five meter HS USB cable
Any Certified USB 2.0 high-speed cable assembly
5
Keypad
Any certified USB keypad
1
The SuperSpeed Interop Tree consists of USB-IF certified, off-the-shelf, consumer devices. The
tree uses either the captive cables on the certified devices, or certified cables to connect the
devices. The USB-IF is not identifying specific makes and models of USB peripherals for the
SuperSpeed Interop Tree. Given the very short shelf-life of most consumer products, it is not
practical to maintain a list of specific products for the SuperSpeed Interop Tree. Thus, the choice
of Certified USB products is the responsibility of the tester.
To verify whether a device is Certified USB, go to the USB-IF Integrators List at:
http://www.usb.org/kcompliance/ilist. Unfortunately, there are numerous uncertified
products that illegally display the Certified USB Logo, so please verify that the product is on the
Integrators List. Should the tester find an uncertified product displaying the Certified USB Logo,
please follow the instructions at
http://compliance.usb.org/index.asp?UpdateFile=Policies#29 to report the
violation to the USB-IF.
At the time of this document’s creation, there are not yet Certified SuperSpeed USB 3.0 hubs or
Certified SuperSpeed USB peripherals for some device classes. Any Certified SuperSpeed USB 3.0
hub or peripheral that is required for this testing procedure and not yet prevalent in the
ecosystem may be substituted with an equivalent known good USB 3.0 hub or SuperSpeed
peripheral.
Furthermore, until the following devices are prevalent in the ecosystem1, this testing procedure
allows substitutions as described in the following table:
If this Certified SuperSpeed
USB peripheral is not
prevalent
use this peripheral
Description
SS low power UASP drive
SS low power drive
Any Certified SuperSpeed USB low-power/selfpowered mass storage device compliant with the Mass
Storage Class
SS video camera
HS video camera
Any Certified USB high-speed video camera compliant
with the Video Class
SS USB cable
SS USB cable
Any available SuperSpeed USB 3.0 cable assembly
This document will be updated when substitutions are no longer acceptable and the same will be
posted on USB.org.
It is highly recommended that vendors expand in-house interoperability testing to include many
more devices and hosts than the minimum required for the SuperSpeed Interop Tree.
The following guidelines will help to select an appropriate product for the SuperSpeed Interop
Tree:
All Devices:
All devices in the SuperSpeed Interop Tree must allow System Suspend and Hibernation
while they are active. Any device that does not allow System Suspend or Hibernation may
not be included in the SuperSpeed Interop Tree.
USB Host System:

The system must be a high performance computer that can handle multiple audio, video
devices with Driver Verifier enabled.






The motherboard needs to have an available slot to add the xHCI controller or have the
xHCI controller integrated.
A fast multiple core processor is required.
Memory and disk storage should be sufficiently large to reduce performance
degradation.
The machine must support S3 suspend.
The machine must support Wake from PCI Express or Wake from Express Card when
the xHCI controller is connected through PCI Express or Express Card.
If the controller has an integrated or embedded hub (as defined in the XHCI
specification), please refer to the diagrams with embedded hubs in each section to build
the correct interop trees.
USB Hubs:
The SuperSpeed Interop Tree exercises five tiers of hubs. The limit to the number of tiers of
hubs in a system is five. This limit is determined by specification limits to the turn-around
time for signals sent from the xHCI controller to reach the device and return back to the xHCI
controller. Any more tiers would not allow these turn-around times to be achievable.
One high-speed hub must have multiple transaction translators (TT), and one high-speed hub
must have single TT. This is required to more fully exercise the xHCI controller’s scheduling
mechanisms.
o
To determine whether a hub has a single TT or multiple TTs connect the hub to
another system and view the properties of the hub in Device Manager. Under the
advanced tab, it will display if the hub has a single TT or multiple TTs.
Demonstrated operation of devices behind full-speed as well as high-speed and USB3.0 hubs
is required since all high-speed peripherals must support full-speed signaling.
The USB 3.0 and high-speed hubs are required to be self-powered, while the compound
keyboards are required to be bus-powered. This is to ensure the SuperSpeed Interop Tree
exercises both self-powered and bus-powered hubs.
USB Mass Storage:
Three Certified USB mass storage devices must be used as Interop Tree devices.



One SuperSpeed Low Power, one high-speed, and one high-speed or full-speed
bulk transport
compliant with the USB Mass Storage Class
o
To determine if a device is high-power, low-power, or self-powered, connect the
device to another system (not the SuperSpeed Interop Tree system). In Device
Manager view devices by connection and select the hub directly upstream of the
device and view that hub’s properties. The Power tab describes how much power
each device uses. A high-power device uses more than 150mA for USB 3.0 devices
and more than 100mA for USB 2.0 devices.
o
The SuperSpeed USB devices must be compliant with the USB Mass Storage UASP
Class when such devices are prevalent in the ecosystem. Otherwise, they must be
compliant with the USB Mass Storage Class.
USB Video Camera:
Two Certified USB video cameras must be used as Interop Tree devices.


One SuperSpeed and one high-speed or full-speed
if a high-speed camera is selected, it must stream video at full-speed correctly
o

isochronous transport
o

To test a high-speed camera, connect the device behind a full-speed hub on another
system (not the USB Host System). Use the software provided with the device to see
if the video camera displays any video, even if it is at a lower resolution. If it does
not display, that video camera cannot work as a SuperSpeed Interop Tree device.
To determine if a camera uses either isochronous transport or bulk transport, either
use a USB bus analyzer or use any USB device analysis software such as USBView.
compliant with the USB Video Class
USB Mouse:
One Certified USB mouse must be used as a SuperSpeed Interop Tree device.




low-speed
interrupt transport
low-power device
compliant with the USB HID Class
USB Display Adapter:
1 Certified USB Display Adapter must be used as a SuperSpeed Interop Tree device.


bulk transport
isochronous transport
USB Headset:
One Certified USB headset must be used as a SuperSpeed Interop Tree device.



isochronous transport
compliant with the USB Audio Class
must have both headphones and a microphone in order to generate traffic heading both
to and from the device
USB cables:
The USB 2.0 specification allows a maximum of 5 meters for a USB cable, and the longest
cables compliant with the USB 3.0 specification are 3 meters in length. To test the worst case
propagation delays, the use of Certified USB five meter high-speed cables and Certified
SuperSpeed USB three meter cables is mandatory. The only exception to this is with regards
to products that have a micro-B type connector. In this instance the required cable length to
connect to the test device is 1 meter.
1.1.1 Equipment Setup
Ensure that the latest BIOS and driver updates are installed for the motherboard by visiting the
vendor’s product support website.
NOTE: U1/U2 MUST BE ENABLED ON BOTH HOSTS AND DEVICES DURING
INTEROPERABILITY TESTING.
1.2
Software
The operating system software required is Windows 8.1.
1.2.1 Install the Operating System
Install Windows 8.1 by either installing a fresh copy or from a previously saved image of the
prepared system given by the steps given below.
Install using default installation options. If you decide to choose custom installation options,
verify that USB Selective Suspend is enabled.
Turn off User Account Control (UAC). This can be found under Control Panel -> User Accounts
and Family Safety -> User Accounts -> Change User Account Control settings and move the
slider bar to the bottom to “Never Notify”.
Turn on Hybrid Sleep. This can be found under Control Panel -> Hardware and Sound -> Power
Options -> Change Plan Settings, then click “Change advanced power settings“, then “Sleep“ ->
“Allow Hybrid Sleep“ and make sure it's set to “On“.
Install the Windows Driver Kit (WDK) 8.1. This is freely available on Microsoft.com. This will be
used to set specific sleep states. At the time of this writing, the WDK 8.1 was used and installed
in the default location, making the scripts reference to the location C:\Program Files\Windows
Kits\8.1\ . Please update this location in the scripts if the WDK has a newer version or is
installed in a different directory.
For each S-State a batch file can be created on the desktop:
Hybrid Sleep:

The Hybrid Sleep batch file, named HybridSleep.bat, should contain the following lines:
C:\Program Files\Windows Kits\8.1\Tools\x86\pwrtest.exe /sleep /c:1 /s:3 /h:y /p:180
echo You may now close this prompt
pause
Hibernate:

The Hibernate batch file, named Hibernate.bat, should contain the following lines:
C:\Program Files\Windows Kits\8.1\Tools\x86\pwrtest.exe /sleep /s:4 /h:n /p:60
echo You may now close this prompt
pause
Connected Standby:

The Connected Standby batch file, named CS.bat, should contain the following lines:
C:\Program Files\Windows Kits\8.1\Tools\x86\pwrtest.exe /cs /c:1 /p:60
echo You may now close this prompt
pause
Shut-Down
 The Shut-Down batch file, named ColdBoot.bat, should contain the following lines:
Shutdown /s /f /t 0
echo You may now close this prompt
pause
Hybrid Shut-Down (Windows 8.1 only)

The Hybrid Shut-Down batch file, named HybridBoot.bat, should contain the following
lines:
Shutdown /s /hybrid /f /t 0
echo You may now close this prompt
pause
Note: If you are using a 64bit operating system, the shortcut above needs to point to “x64”
instead of “x86”. Test out this shortcut to ensure that it hibernates the machine correctly before
continuing.
Install any required platform-specific drivers for the USB Host System. All devices other than the
xHCI controller in the USB Host System should be “working properly”, i.e. no yellow
exclamation points visible in Device Manager. There should also be no “unknown devices”
shown in the Device Manager.
Use Windows Update to obtain all the latest service packs and recommended updates for the
operating system.
Enable Driver Verifier on the xHCI controller driver, all drivers for devices in the SuperSpeed
Interop Tree, and drivers for the Device Under Test. The list of drivers can be found in Chapter 8,
Appendix A of this document. To enable Driver Verifier for these drivers:
Determine the name of the .sys files for the drivers.



Connect the xHCI Interoperability Tree to another system running Windows 8.1 and
the same architecture (x86 or x64) as the USB Host System.
Install the driver for the xHCI controller on the other system.
For each device in the xHCI Interoperability Tree:
o Follow the vendor-recommended install procedure on the other system.
o Open device manager and find the device in the tree.
o Right click on the device and select to view the device’s properties.
o Under the driver tab, press “Driver Details”.
o Copy down the name of all of the .sys files located in the list.
Move to the System being used for the test.









Open the run box (press the Windows Key + R together).
Type the command “Verifier”.
Select “Create custom settings (for code developers)”.
Select “Enable predefined settings”
Check all of the checkboxes except for “Low resources simulation”.
Select “Select driver names from a list”.
For each driver that was copied down before and isn’t in this list:
o Select “Add currently not loaded drivers to the list”.
o Type in the name of the .sys files for the driver and press “Open”.
o Select that driver in the list
In the Driver Verifier Manager, check all of the checkboxes for the driver names you
added to the list and press “Finish”.
Reboot the machine.
While running the xHCI Interoperability tests if there is a crash in a Microsoft driver, then the test
is a tentative fail. The crash will need to be investigated to determine if it’s a 3 rd party driver issue
or a Microsoft driver issue. If you hit a recurring crash on boot, disconnect the Interop Tree and
enter safe mode on Windows. Then run “Verifier /reset” to turn off the verifier.
1.2.2 Determining System Supported Low-Power States
Some systems do not support all low power states: S3, S4 and Connected Standby. The states a
system does support must be tested, however. To determine what states a system supports use
pwrtest.exe as described in section 1.2.1.
Note: The system used to test peripherals and hubs must support S3 and S4.
o
o
o
o
Open Command Prompt
Navigate to the location of pwrtest.exe
Type: “pwrtest.exe /info:powercap”
Press Enter
A list of supported system states will show, if the state is flagged as “1” it is supported, if it is
flagged as “0” it is not supported. For Example if pwrtest returns:
SystemS3StateSupported = 1
SystemS4StateSupported = 1
AoAc
=0
This means S3 and S4 are supported, Connected Standby is not supported (Connected Standby
support is shown by AoAc).
It is important to note that some systems may support a state but will not function in that state. It
is important to test how USB functions with all states that are supported on a given system.
1.2.3 Software Logistical Overview
Certification is permitted using Windows 8.1. Testing other operating systems is encouraged, but
not required.
Testing must be performed on a new and clean installation of the operating system. Instead of
formatting the drive and installing the OS before every test run, using a disk imaging utility to
restore a copy of a clean OS is acceptable.
A means of validating the data after transfer to/from the mass storage device is required. Using
a utility, such as WinZip Computing Inc.’s WinZip®, which automatically performs a CRC on its
data, or jZip, which can manually validate the data of a .zip file, is acceptable to validate the data.
Three files are required for the data transfers in the xHCI Interoperability tests: A 30MB+ .zip file
on the HS Low Power Drive, a 1GB+ .zip file on the HS Drive, and a 2GB+ .zip file on the SS High
Power Drive.
The USB host system must be virus scanned 1before the test can begin. All mass storage devices
(including the DUT if applicable) must be virus scanned before beginning the tests.
1.3
xHCI Interoperability Test Verification
Before running the xHCI Interoperability tests with a newly created Interop Tree, run the tests
without the DUT first and with a similar Certified USB device instead. Ensure that all tests pass.
If a test does not pass, investigate what software, driver, or device could be causing the failure.
The xHCI Interoperability tests were designed to pass when run on any Certified USB device, so
any issues that arise from testing with the Certified USB device should be resolved before testing
the device under test.
1.4
xHCI Interoperability Logistical Overview
Effectively, xHCI Interoperability is a consumer experience test of the product. It examines the
product's ability to function correctly in normal system configurations. The following discussion
is the rationale for the xHCI Interoperability tests so that the procedures can be modified to
adequately test a product for compliance.
Because the primary features of USB are its "hot-plugging" and "plug and play" capabilities, the
dynamic attachment of a USB peripheral is a tenet of USB certification for peripherals and hosts.
All USB capable hosts and USB peripherals must be able to operate correctly on attachment and
re-attachment of the peripheral. After the testing system is identified as a stable environment
before running test, if any enumeration attempt fails, the test must be recorded as a fail.
No Silent Failure rule – USB devices are not allowed to appear broken without providing
feedback to the consumer about the cause of the problem and how to correct. Thus, compliance
enforces a "no silent failure" rule on hosts and peripherals in special situations where the device
appears broken. Typically, the "no silent failure" is implemented when the peripheral is not
supported by the host, there is insufficient bandwidth on the bus for the peripheral to operate, or
there is insufficient power available. When implemented, the message must appear on the host
machine and not just in documentation. There must be enough information for the consumer to
understand why the device does not work. In other words, a USB device is never to appear
1
In order not to disrupt test run, virus-scan should be set in manual mode. This prevents auto-scans from
happening during the testing.
broken without justification and explanation to the consumer.
Consumer experience is the most important factor when assessing a Pass or Fail result. If the test
result yields any kind of negative consumer experience, the test must be recorded as a fail.
Caution should be used when testing out of sequence with the steps outlined. This test
procedure is scripted and individual steps may be dependent upon previous test steps having
been performed.
2 USB Peripheral Interoperability Test Steps
Construct the SuperSpeed Interop Tree as outlined in Figure 2-1. If the host system contains an
embedded hub construct the SuperSpeed Interop Tree as outlined in Figure 2-2 instead. Do not
attach the SuperSpeed Interop Tree to the xHCI controller.
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
DUT
Mouse
HS/FS
Camera
Figure 2-1: SuperSpeed Interop Tree with Device Under Test
SS Video
Camera
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
DUT
Mouse
HS/FS
Camera
Figure 2-2: SuperSpeed Interop Tree with Device Under Test (embedded hub)
SS Video
Camera
Tier Device
1
2
 Hub SS1– Self-powered USB3.0 Hub attached to the xHCI controller
 Hub SS2 - Self-powered USB3.0 Hub on port 1 of Hub SS1
 Hub SS3 - Self-powered USB3.0 Hub on port 1 of Hub SS2
3
4
 Hub SS4 - Self-powered USB3.0 Hub on port 1 of Hub SS3-STT
5
 Hub SS5 - Self-powered USB3.0 Hub on port 1 of Hub SS4
6
 SS Low Power Drive on port 1 of Hub SS5
6
 SS Video Camera on port 2 of Hub SS5
6
 Device Under Test on port 3 of Hub SS5
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
5
 HS Drive on port 1 of Hub HS5
6
 Display Adapter on Port 3 of SS4
5
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
3
4
 FS Drive on port 2 of Hub FS3-1
4
 Keypad on port 4 of FS3-1
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
3
4
 FS Video Camera on port 1of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
2.1
1.
Peripheral Interoperability Tests
xHCI Controller Driver Installation
Ensure that the USB Host System has a clean install of the OS and the OS is configured as
described in Section 1.2.1. Turn off the USB Host System and install the xHCI controller into
the USB Host System if it is not already integrated.
Power on the USB Host System. One of three scenarios is acceptable for the USB Host System
to install the xHCI controller driver:
o
The OS identifies and automatically installs the xHCI controller driver.
o
The OS displays that it cannot find the driver for the xHCI controller. Follow the vendorrecommended install procedure to complete the driver install.
o
If the xHCI controller is already integrated into the USB Host System, then the OS
displays nothing, as it has already attempted install for the xHCI controller with the
initial install of the OS. Follow the vendor-recommended install procedure to complete
the driver install.

Pass:
1.
2.
3.

2.
(The OS identifies and automatically installs the xHCI controller driver
OR
The vendor-recommended install procedure installs the xHCI controller driver)
AND
The xHCI controller driver is installed correctly and operates (no yellow exclamation point is displayed in
device manager)
Fail:
1. The xHCI controller driver does not install
OR
2. The xHCI controller driver is installed correctly but is non-operational (yellow exclamation point is
displayed in device manager)
Peripheral Enumeration and Driver Installation
Do not install any drivers or software for any device in the SuperSpeed Interop Tree prior to
attaching the SuperSpeed Interop Tree to the xHCI controller.
Attach the SuperSpeed Interop Tree by connecting SS1 into any port on the xHCI controller.
o
If the xHCI controller has an embedded hub, then unplug Hub SS3 and Hub SS4; re-plug
Hub SS4 directly into port one of Hub SS2.
For each device in the SuperSpeed Interop Tree (including the DUT) follow the vendorrecommended install procedure. Ensure that all drivers listed for each device in the
SuperSpeed Interop Tree match what is currently being tested under Driver Verifier. To
display the existing drivers being verified by Driver Verifier:
o
o
o
Open the run box (press the Windows Key + R together).
Type the command “Verifier”.
Select “Display existing settings”

Pass:
1. All SuperSpeed Interop Tree devices enumerate
AND
2. All SuperSpeed Interop Tree devices drivers are installed either automatically or through the vendor
recommended install procedure
AND
3. All SuperSpeed Interop Tree devices do not require a reboot
AND
4. All SuperSpeed Interop Tree devices are correctly identified by Device Manager and no yellow
exclamation point is shown for any device
AND
5. (Software installs without any software crashes or a blue screen
OR
6. No software required)

Fail:
1. Any device cannot be installed because it requires driver installation or application software BEFORE the
device is ever plugged in
OR
2. Any device does not enumerate or blue screens during enumeration
OR
3. Any device requires a reboot
OR
4. Any device is incorrectly identified by Device Manager or any device is flagged as not operational (yellow
exclamation point)
5.
3.
OR
Installation software crashes or causes a blue screen
Interoperability
o
Operate all the devices in the SuperSpeed Interop Tree.

Whenever the Peripheral Interoperability Test Steps state to operate all of the
devices in the SuperSpeed Interop Tree, this involves operating the following steps
concurrently:

Operate the microphone in the Video Cameras by speaking into the microphone
and viewing the input sound monitor

This can be found under Control Panel -> Hardware and Sound -> Sound
under the “Recording” tab

View streaming video from the SS Video Camera

View streaming video from the FS Video Camera
Poor video quality may be seen when Driver Verifier is enabled. If there was
poor quality, continue testing with the Driver Verifier enabled for all
Interoperability steps. Repeat all Interoperability steps with Driver Verifier
off. USB-IF will compare Interoperability results with Driver Verifier
Enabled and Disabled to determine Pass/Fail for certification.

Transfer a 30+ MB file from the SS Low Power Drive to the FS Drive

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter

Operate the Device Under Test


If the DUT is a SS Mass Storage Device, then transfer a 4GB+file from the SS
Low Power Drive to the DUT and transfer a 1GB+file from the DUT to the
HS Drive
If the DUT is a device other than Mass Storage Device, then ensure the
operation on the DUT overlaps over the period of time that other devices in
the tree are operating.

Strike keys on keypad

Move the mouse
o
Verify that all devices are operating concurrently. Verify the Device Speed using the
USBView utility.

Pass:
All SuperSpeed Interop Tree devices operate correctly

4.
All Devices Tests
o
5.
Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
Run tests 1-7 as specified in Chapter 7.
Topology Change 1
o
Operate all the devices in the SuperSpeed Interop Tree except the Device Under Test.
o
While operating the devices, detach the Device Under Test from port 3 on Hub SS5
o
While operating the devices, reattach the Device Under Test to port 4 on Hub HS5 as
shown in Figure 2-3 and Figure 2-4.
xHCI
DUT
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
X
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS4
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 2-3: Topology Change 1
SS Video
Camera
xHCI
DUT
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
X
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 2-4: Topology Change 1 (embedded hub)
6.
o
Verify that all devices except for the Device Under Test continue to operate concurrently.
o
Operate the Device Under Test.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests
o
7.
Run tests 1-7 as specified in Chapter 7.
Topology Change 2 (For Low/Full-speed capable USB Devices only)
o
Operate all the devices in the SuperSpeed Interop Tree except the Device Under Test.
o
While operating the devices, detach the Device Under Test from port 4 on Hub HS5.
o
While operating the devices, attach the Device Under Test to port 3 on Hub FS3-1 as
shown below in Figure 2-5 and Figure 2-6.
xHCI
DUT
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
X
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 2-5: Topology Change 2 - Low/Full-Speed capable devices only
SS Video
Camera
xHCI
DUT
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
X
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 2-6: Topology Change 2 - Low/Full-Speed capable devices only (embedded hub)
8.
o
Verify that all devices except for the Device Under Test are continuing to operate
concurrently.
o
Operate the Device Under Test.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
Interoperability without Driver Verifier
o
Run this test only if there was poor video or audio quality when operating all of the
devices in the SuperSpeed Interop Tree. Run all interoperability test steps including
topology change 1 and topology change 2.
o
9.
Disable Driver Verifier:

Open the run box (press the Windows Key + R together)

Type the command “Verifier”

Select “Delete Existing Settings” and press Finish. Press “Yes” and restart the
machine.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly. For certification purposes USB-IF will compare results
between Driver Verifier Enabled and Driver Verifier Disabled to determine Pass/Fail.

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
Function Wake
o
If the DUT supports function remote wake, it should have an interface for users to initiate
function wake. To run this test, operate all the devices in the SuperSpeed Interop Tree
o
While operating the devices, put the system to sleep by going to the Start menu, select
the arrow next to the Shut Down button, and then choose Sleep.
o
Initiate function wake from one of the functions on the device to wake the system up.
o
Upon resuming, verify that the file transfers continue without error.
o
Close any software that is used for any SuperSpeed Interop Tree device operation and
close the “Recording” tab window.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.
o
Repeat this test for all functions that support wake. (The “Device Summary” test of
Command Verifier 3.0 identifies all functions (interfaces) that support function wake.

1.
5.
Pass:
System sleeps
AND
System resumes
AND
File transfers continue without error
AND
All devices can function after resuming
AND
All functions that advertise wake capability will wake the machine

1.
Fail:
System does not sleep
2.
3.
4.
2.
3.
4.
5.
6.
OR
System does not resume
OR
System blue screens / locks up
OR
Any device cannot function after resuming
OR
File transfers do not continue after resuming
OR
Function that supports wake doesn’t wake machine
10. Root Port Testing
o
Connect DUT to one of root ports of xHCI host. Run tests 1-7 as specified in Chapter 7.

Pass:
All the tests 1-7 of Chapter 7 PASS

Fail:
If any of the tests 1-7 of Chapter 7 FAIL
2.2
Peripheral Current Measurement
Devices operating at SuperSpeed are allowed to draw a maximum configured current of
900mA and unconfigured current of 150mA*. Devices operating at High-Speed or below may
draw a maximum configured current of 500mA and unconfigured current of 100mA*.
Devices must report their maximum configured current draw and their power configuration
as self or bus powered to the host and must operate within the regions reported. Additionally
any device that is in the suspended state may draw no more than 2.5mA*.
If device has external power, check whether it enumerates without it and if so then run tests
with device configured as bus-powered.
o
o
o
o
o
o
o
o
Install USB30CV from the USB-IF SuperSpeed Tools page.
Connect a SuperSpeed Current Measurement Fixture between DUT and xHCI host as
shown in Figure 2-7.
Set up a Multimeter to measure current drawn from device.
Run “Current Measurement [3.0 Devices]“ test in Command Verifier.
Read meter at each prompt.
Read the value of “Max Power Consumption” from the log.
Read device type from the log: bus-powered, self-powered or both.
Record following values:
 Bus, Both or Self-Powered
 The current in unconfigured mode
 Current in configured mode
 Current in U0



o
o
Current in U1
Current in U2
Current in U3
Reload the xHCI controller driver being used for Interop.
Operate the device
* These tests assume that if the device has a battery, that the battery is a Good Battery, as defined in the Battery Charging
Specification, Revision 1.2
o
Record the highest measured current value
o Repeat all steps again with device operating at High-speed by changing SuperSpeed
cable with High-speed cable (Note: U0, U1, U2 and U3 are not applicable in High-speed
mode) use CV tests labeled “Current Measurement Test [2.0 Devices]”
DUT
xHCI
Current Measurement
Fixture
Figure 2-7: Peripheral Current Measurement Topology

Pass:
1. Device reports Self-Powered while operating as self-powered if supported
AND
2. Device reports Bus-Powered while operating as bus-powered if supported
AND
3. Max Power Consumption reported is 900mA or less when operating at SuperSpeed and 500mA or less
when operating at High-speed or Full-Speed
AND
4. Measured Unconfigured Current is 150mA or less when operating at SuperSpeed and 100mA or less when
operating at High-speed or Full-Speed
AND
5. Measured Current during device operation, U0, U1 and U2 is less than or equal to reported Max Power
Consumption
AND
6. Measured Current in U3 is less than or equal to 2.5mA and reported Max Power Consumption

Fail:
1. Device reports Bus-Powered while operating as self-powered
OR
2. Device reports Self-Powered while operating as bus-powered
OR
3. Max Power Consumption reported is greater than 900mA when operating at SuperSpeed and greater than
500mA when operating at High-speed or Full-Speed
OR
4. Measured Unconfigured Current is greater than 150mA when operating at SuperSpeed or greater than
100mA when operating at High-speed or Full Speed
OR
5. Measured Current during device operation, U0, U1 or U2 is greater than reported Max Power
Consumption
OR
6. Measured Current in U3 is greater than 2.5mA or reported Max Power Consumption
2.3
Peripheral U1/U2 Test Steps
o
o
o
o
o
o
o
o
Connect a USB 3.0 hub to an exposed host port.
Connect a DUT to a downstream hub port with a USB Protocol Analyzer between the
hub and device.
Trace USB traffic including idle device time and normal DUT operation.
Verify that the link successfully enters U1 or U2.
Verify that the hub correctly sends a deferred packet to the DUT and to the host.
Verify that the DUT correctly sends an ERDY after the deferred packet.
Verify that the host re-sends the packet with the deferred bit cleared.
Verify that the DUT completes the re-sent packet.

Pass:
1. Link successfully enters U1 or U2
AND
2. Link returns to U0 and the original packet that was sent during U1/U2 is successfully completed

Fail:
1. Link remains in U0
OR
2. Re-Sent packet does not complete correctly
2.4
Peripheral L1 Test Steps
o
o
o
o
o
Connect a USB Peripheral to the LPM PDK host with a USB Protocol Analyzer in
between the device and the LPM PDK host. The USB peripheral is to be connected to
operate in High-speed mode.
Operate the device. For example if it’s a MSC device, transfer a file to the drive.
Trace USB traffic including enumeration, idle device time and normal DUT operation.
Verify that the device successfully enters L1.
Verify that the device successfully resumes to L0 and functions normally.

Pass:
Device successfully enters and exits L1 and device operates normally

Fail:
If device does not enter L1 and does not operate normally
3 USB Self-Powered Hub Interoperability Test Steps
For Self-Powered Hub testing, two Hubs Under Test are required.
Construct the SuperSpeed Interop Tree as outlined in Figure 3-1. If using a system with an
embedded hub construct the SuperSpeed Interop Tree as outlined in Figure 3-2 instead. Do not
attach the SuperSpeed Interop Tree to the xHCI controller.
xHCI
SS
Cable
(3m)
SS Cable (3m)
HUT
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 3-1: SuperSpeed Interop Tree with Self-Powered Hub Under Test
SS Video
Camera
xHCI
SS
Cable
(3m)
SS Cable (3m)
HUT
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 3-2: SuperSpeed Interop Tree with Self-Powered Hubs Under Test (embedded hub)
Tier Device
1
2
3
 Hub SS1– Self-powered USB3.0 Hub Under Test (HUT) at Root Port
 Hub SS2 - Self-powered USB3.0 Hub on port 1 of Hub SS1
 Hub SS3 - Self-powered USB3.0 Hub on port 1 of Hub SS2
4
 Hub SS4 - Self-powered USB3.0 Hub on port 1 of Hub SS3
5
 Hub SS5– Self-powered USB3.0 Hub Under Test (HUT) on port 1 of
Hub SS4
6
 SS Low Power Drive on port 1 of Hub SS5
6
 SS Video Camera on port 2 of Hub SS5
5
6
5
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
 HS Drive on port 1 of Hub HS5
 Display Adapter on Port 3 of SS4
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
3
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
4
 FS Drive on port 4 of Hub FS3-1
4
 Keypad on port 2 of FS3-1
3
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
4
 FS Video Camera on port 1of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
3.1
1.
Self-Powered Hub Interoperability Tests
xHCI Controller Driver Installation
Ensure that the USB Host System has a clean install of the OS and the OS is configured as
described in Section 1.2.1. Turn off the USB Host System and install the xHCI controller into
the USB Host System if it is not already integrated.
o Ensure that the SuperSpeed Interop Tree is not attached to the xHCI controller or
embedded hub.
Power on the USB Host System. One of three scenarios is acceptable for the USB Host System
to install the xHCI controller driver:
2.
o
The OS identifies and automatically installs the xHCI controller driver.
o
The OS displays that it cannot find the driver for the xHCI controller. Follow the vendorrecommended install procedure to complete the driver install.
o
If the xHCI controller is already integrated into the USB Host System, then the OS
displays nothing, as it has already attempted install for the xHCI controller with the
initial install of the OS. Follow the vendor-recommended install procedure to complete
the driver install.

Pass:
1. (The OS identifies and automatically installs the xHCI controller driver
OR
2.
The vendor-recommended install procedure installs the xHCI controller driver)
AND
3. The xHCI controller driver is installed correctly and operates (no yellow exclamation point is displayed in
device manager)

Fail:
1. The xHCI controller driver does not install
OR
2. The xHCI controller driver is installed correctly but is non-operational (yellow exclamation point is
displayed in device manager)
Peripheral Enumeration and Driver Installation
Do not install any drivers or software for any device in the SuperSpeed Interop Tree prior to
attaching the SuperSpeed Interop Tree to the xHCI controller.
Attach the SuperSpeed Interop Tree by connecting the Hub Under Test SS1 into any port on
the xHCI controller.
For each device in the SuperSpeed Interop Tree follow the vendor-recommended install.
Ensure that all drivers listed for each device in the SuperSpeed Interop Tree match what is
currently being tested under Driver Verifier. To display the existing drivers being verified by
Driver Verifier:
o
o
o
Open the run box (press the Windows Key + R together).
Type the command “Verifier”.
Select “Display existing settings”
3.

Pass:
1. All SuperSpeed Interop Tree devices enumerate
AND
2. All SuperSpeed Interop Tree devices drivers are installed either automatically or through the vendor
recommended install procedure
AND
3. All SuperSpeed Interop Tree devices do not require a reboot
AND
4. All SuperSpeed Interop Tree devices are correctly identified by Device Manager and no yellow
exclamation point is shown for any device
AND
5. (Software installs without any software crashes or a blue screen
OR
6. No software required)

Fail:
1. Any device cannot be installed because it requires driver installation or application software BEFORE the
device is ever plugged in
OR
2. Any device does not enumerate or blue screens during enumeration
OR
3. Any device requires reboot
OR
4. Any device is incorrectly identified by Device Manager or any device is flagged as not operational (yellow
exclamation point)
OR
5. Installation software crashes or causes a blue screen
Interoperability
Examine the Hub Under Test and identify all USB connections.
Each and every USB port on the Hub Under Test must be able to pass all
required tests. The xHCI Interoperability Tests operate three ports of the Hub
Under Test at a time. All ports must be tested in at least one topology.
o
o
Operate all the devices in the SuperSpeed Interop Tree.

Whenever the Self-Powered Hub Interoperability Test Steps state to operate all of the
devices in the SuperSpeed Interop Tree, this involves operating the following steps
concurrently:
o
Operate the microphone in the Video Cameras by speaking into the microphone
and viewing its input level

This can be found under Control Panel -> Hardware and Sound ->
Sound under the “Recording” tab.

View streaming video from the SS Video Camera

View streaming video from the FS Video Camera
Poor video quality may be seen when Driver Verifier is enabled. If there was
poor quality, continue testing with the Driver Verifier enabled for all
Interoperability steps. Repeat all Interoperability steps with Driver Verifier
off. USB-IF will compare Interoperability results with Driver Verifier
Enabled and Disabled to determine Pass/Fail for certification.
4.
Transfer a 30+ MB file from the SS Low Power Drive to the FS Low Power Drive

Transfer a 1+ GB file from the HS Drive to the SS High Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter

Strike keys on the keypad

Move the mouse
o
Verify that all devices are operating concurrently. Verify the Device Speed using the
USBView utility.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests
o
5.

Run tests 1-7 as specified in Chapter 7.
Topology Change 1
o
Stop all SuperSpeed Interop Tree device operation!
o
Detach the Hub Under Test SS1 from the xHCI controller and detach all attached devices
from the Hub Under Test SS1.
o
Reattach the Hub Under Test SS1 to port 3 of Hub SS2. Then attach Hub HS2-MTT to
port 2 of Hub SS2 and Hub HS3-STT to port 3 of the Hub Under Test SS1. Then attach
Hub FS3-1 to port 1 of the Hub Under Test SS1. Then attach Hub FS3-2 to port 2 of the
Hub Under Test SS1 as shown in Figure 3-3 and Figure 3-4.
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS2
SS Cable (3m)
Hub
SS3
Hub
SS4
SS
Cable
(3m)
HS Cable (5m)
HS Cable (5m)
Hub
HS2-MTT
HUT
SS1
SS Cable (3m)
HS
Cable
(5m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
Mouse
HS/FS
Drive
HS/FS
Camera
Keypad
Figure 3-3: Topology Change 1
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS2
Hub
SS4
SS
Cable
(3m)
HS Cable (5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
HUT
SS1
HS
Cable
(5m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS
Cable
(5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
SS Video
Camera
Figure 3-4: Topology Change 1 (embedded hub)
o
Operate the microphones and FS Video Camera. Also operate all SS devices in the tree.

If the Hub Under Test is a Single-TT Hub, then it is acceptable for the headset,
microphones, or FS Video Camera to not work, as the configuration may require
more bandwidth than the Hub Under Test can provide. The test setup must then be
restored to a configuration that has enough bandwidth.
i. Detach Hub FS3-2 from port 2 on the Hub Under Test and attach the
Hub FS3-2 to port 1 on Hub HS3-STT. This should set the configuration
to what is displayed in Figure 3-5 and Figure 3-6.
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS3
Hub
SS2
SS
Cable
(3m)
HS Cable (5m)
HS Cable (5m)
Hub
HS2-MTT
HUT
SS1
SS Cable (3m)
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
X
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 3-5: Topology Change 1 - Single-TT Hubs Only
SS Video
Camera
xHCI
Hub
SS2
Hub
SS4
SS
Cable
(3m)
HS Cable (5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
HUT
SS1
HS
Cable
(5m)
HUT
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
X
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 3-6: Topology Change 1 - Single-TT Hubs Only (embedded hub)
o


6.
Pass:
All SuperSpeed Interop Tree devices operate correctly
Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly.
All Devices Tests
o
7.
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.
`
Run tests 1-7 as specified in Chapter 7.
Topology Change 2
o
Stop all SuperSpeed Interop Tree device operation!
o
Operate the following devices concurrently:
o

View streaming video from the SS Video Camera

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter
While operating the devices, detach the Hub Under Test from SS2 and detach all attached
devices from the Hub Under Test.
o
Detach Hub FS3-1 from Port 1 on Hub SS1. Attach Hub FS3-1 to Port 1 on HS2-MTT
o
Detach HS3-STT from Hub SS1 and attach Hub HS3-STT to Port 2 of Hub HS2-MTT
o
Detach Hub FS3-2 from Hub SS1 and remove all devices from Hub FS3-2. Attach Hub
FS3-2 to port 2 of HS3-STT
o
Attach Hub SS1 to Port 3 of Hub HS3-STT. Attach Mouse and Camera to Ports 1 and 2 of
Hub SS1 as shown in Figure 3-7 and Figure 3-8
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS2
SS Cable (3m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HUT
SS5
HS Cable (5m)
HS
Cable
(5m)
Hub
HS2-MTT
Hub
HS3-STT
HS
Cable
(5m)
SS Cable (3m)
SS
Display
Adapter
SS Low
Power Drive
HUT
SS1
Hub
HS5
HS
Cable
(5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS/FS
Camera
Mouse
HS
Drive
HS/FS
Drive
Keypad
Figure 3-7: Topology Change 2
SS Video
Camera
xHCI
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS2
Hub
SS4
HUT
SS5
HS Cable (5m)
Hub
HS2-MTT
HS
Cable
(5m)
SS Cable (3m)
HS
Cable
(5m)
Hub
HS3-STT
SS
Display
Adapter
SS Low
Power Drive
HUT
SS1
Hub
HS5
HS
Cable
(5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS/FS
Camera
Mouse
HS
Drive
HS/FS
Drive
Keypad
Figure 3-8: Topology Change 2 (embedded hub)
8.
o
Verify that the file transfer continues to take place.
o
Verify that the SS Video Camera continues to function.
o
Verify that SS Display Adapter continues to show video and play audio.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
1. After the topology change the file transfer continued to take place
AND
2. After the topology change the SS Video Camera continues to function
AND
3. After the topology change the SS Display Adapter continues to function
AND
4. All SuperSpeed Interop Tree devices operate correctly

Fail:
1. After the topology change the file transfer was cancelled
OR
2. After the topology change the SS Video Camera stopped functioning
OR
3. After the topology change the SS Display Adapter stopped functioning
OR
4. One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests
SS Video
Camera
o
9.
Run tests 1-7 as specified in Chapter 7.
Interoperability without Driver Verifier
o
Run this test only if there was poor video or audio quality when operating all of the
devices in the SuperSpeed Interop Tree. Run this test for each Topology that there was
poor video or audio quality.
o
Disable Driver Verifier:
o

Open the run box (press the Windows Key + R together)

Type the command “Verifier”

Select “Delete Existing Settings” and press Finish. Press “Yes” and restart the
machine.
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
10. Function Wake
3.2
o
Connect a function-remote-wake capable SuperSpeed device to one of hub ports on the
5th SuperSpeed Hub (HUT SS5)
Put the system into sleep
o
Wake up the system by the function-remote-wake interface on the SuperSpeed device

Pass:
The system wakes up normally.

Fail:
The system has any abnormal behaviors.
Self-Powered Hub Current Measurement
Self-Powered Hubs operating at SuperSpeed are allowed to draw a maximum current of
150mA. Self-Powered Hubs operating at High-speed or below may draw a maximum current
of 100mA. Self-Powered Hubs must report its own maximum current draw and power
configuration as self-powered to the host and must operate within the regions reported.
Additionally any device that is in the suspended state may draw no more than 2.5mA.
Check whether Self-Powered Hub operates as Bus-Powered by removing external power. If
so tests need to be run according to Bus-Powered hub rules (See Chapter 4).
o
o
o
o
o
o
o
o
o
o
o
Install USB30CV from the USB-IF SuperSpeed Tools page.
Connect a SuperSpeed Current Measurement Fixture between HUT and xHCI host as
shown in Figure 3-9.
Set up a Multimeter to measure current drawn from hub.
Run “Current Measurement [3.0 Devices]“ test in Command Verifier.
Read meter at each prompt.
Read the value of “Max Power Consumption” from the log.
Read hub type from the log: bus-powered, self-powered or both.
Record following values:
 Bus, Both or Self-Powered
 The current in un-configured mode.
 Current in configured mode
 Current in U0
 Current in U1
 Current in U2
 Current in U3
Reload the xHCI controller driver being used for Interop..
Record the highest measured current value
Repeat all steps again with hub operating at High-speed by changing SuperSpeed cable
with High-speed cable (Note: U0, U1, U2 and U3 are not applicable in High-speed mode)
use CV tests labeled “Current Measurement Test [2.0 Devices]”
xHCI
Current Measurement
Fixture
HUT
Figure 3-9: Hub Current Measurement Topology

Pass:
1. Hub reports Self-Powered and does not operate as Bus-Powered
AND
2. Max Power Consumption reported is 150mA or less when operating at SuperSpeed and 100mA or less
when operating at High-speed or Full-Speed
AND
3. Measured Current during device operation, U0, U1 and U2 is less than or equal to reported Max Power
Consumption
AND
4. Measured Current in U3 is less than or equal to 2.5mA and reported Max Power Consumption

3.3
3.4
Fail:
1. Hub reports Self-Powered but is capable of enumerating as Bus-Powered
OR
2. Max Power Consumption reported is greater than 150mA when operating at SuperSpeed or greater than
100mA when operating at High-speed or Full-Speed
OR
3. Measured Current during hub operation, U0, U1 or U2 is greater than reported Max Power Consumption
OR
4. Measured Current in U3 is greater than 2.5mA or reported Max Power Consumption
Self-Powered Hub U1/U2 Test Steps
o
Connect the HUT to an exposed host port.
o
Connect a KGD to a downstream hub port with a USB Protocol Analyzer between the
hub and device.
o
Trace USB traffic including idle device time and normal KGD operation.
o
Verify that the link successfully enters U1 or U2.
o
Verify that the hub correctly sends a deferred packet to the KGD and to the host.
o
Verify that the KGD correctly sends an ERDY after the deferred packet.
o
Verify that the host re-sends the packet with the deferred bit cleared.
o
Verify that the KGD completes the re-sent packet.

Pass:
1. Link successfully enters U1 or U2
AND
2. Link returns to U0 and the original packet that was sent during U1/U2 is successfully completed

Fail:
1. Link remains in U0
OR
2. Re-sent packet does not complete successfully
Self-Powered Hub LPM Tests
Download the MUTT Software Package from Microsoft. Double click and install the MSI file.
After the install finishes the contents of the package will most likely be found under
C:\Program Files\USBTest\
Choose either the x86 or the x64 folder depending upon the system OS. Inside the folder
select the tool labeled UsbLPM.
Selective Suspend must be disabled when using the Usb LPM Tool. Go to Control Panel ->
Power Options -> Change Plan Settings -> Change advanced power settings. Under “USB
settings” choose “USB selective suspend setting” and set it to “Disabled”.
Note: The hub is required to be in an equal or higher link state than any device(s) attached to
its downstream port(s). If at any time the hub goes to a lower link state than an attached
device the hub fails testing.
1.
Inactivity U1/U2 Entry Test – Hub Only
Open the Usb LPM Tool
o
Configure the Hub Under Test as shown in Figure 3-10 and attach it to an xHCI port.
xHCI
HUT
Figure 3-10: Hub Only Topology
Let the hub remain inactive for a few seconds and observe whether it enters U1 or U2.
2.

Pass:
Hub enters U1 or U2

Fail:
Hub remains in U0
Inactivity U1/U2 Entry Test – Hub and U1/U2 Enabled Device
o
o
o
Detach hub from the host.
Attach a SuperSpeed, U1/U2 enabled device to the hub.
Attach tree to the host as shown in Figure 3-11.
xHCI
HUT
SS1
U1/U2
Enabled
Figure 3-11: Hub and U1/U2 Enabled Device
Allow the devices to remain inactive. Observe the LPM tool, the device should enumerate
and both the host and the device should enter U1 or U2.
3.

Pass:
1. Both device and hub enter U1 or U2
OR
2. The hub enters U1 and the device enters U2

Fail:
1. Either the hub and/or device remain in U0
OR
2. The device enters U1 while the hub enters U2 or U3
OR
3. The device enters U2 while the hub enters U3
Inactivity U1/U2 Entry Test – Hub and U1/U2 Disabled Device
o
o
o
Detach hub from the host.
Attach a SuperSpeed, U1/U2 disabled device to the hub.
Attach tree to the host as shown in Figure 3-12.
xHCI
HUT
SS1
U1/U2
Disabled
Figure 3-12: Hub and U1/U2 Disabled Device
Allow the devices to remain inactive. Observe the LPM tool, the device should enumerate
and the hub should not enter U1 or U2 (assuming device remains in U0).
4.

Pass:
Hub remains in U0 with device

Fail:
Hub enters U1, U2 or U3 while device remains in U0
Active LPM Test
The USB LPM Tool has an active mode where it can request the device and hub to enter U1
or U2 and report a pass/fail. Because this test does not necessarily exhaust all possibilities
during U1/U2 testing it should be run 10 times.
o
Attach the configuration shown in Figure 3-11 to an available xHCI port.
o
In the Mode of operation box select the option “testing”.
o
Select the SuperSpeed hub from the list as shown in Figure 3-13.
o
Click the “Start” button on the right.
o
Observe the test report for failures or errors during the test cases.
o
Repeat this test 9 more consecutive times

Pass:
All 10 consecutive test cases report “pass”

Fail:
1 or more consecutive test cases reported a “fail” or “error”
Figure 3-13: Usb LPM Tool Interface
4 USB Bus-Powered Hub Interoperability Test Steps
TBD.
5 USB Host Interoperability Test Steps
Construct the SuperSpeed Interop Tree as outlined in Figure 5-1. If the host under test contains an
embedded hub construct the SuperSpeed Interop Tree as outlined in Figure 5-2 instead. Do not
attach the SuperSpeed Interop Tree to the Host Under Test.
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-1: SuperSpeed Interop Tree with Host Under Test
SS Video
Camera
xHCI
SS Cable (3m)
SS Cable (3m)
SS
Cable
(3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-2: SuperSpeed Interop Tree with Host Under Test (embedded hub)
SS Video
Camera
Tier Device
1
 Hub SS1– Self-powered USB3.0 Hub attached to the xHCI controller under test
 Hub SS2 - Self-powered USB3.0 Hub on port 1 of Hub SS1
2
 Hub SS3 - Self-powered USB3.0 Hub on port 1 of Hub SS2
3
 Hub SS4 - Self-powered USB3.0 Hub on port 1 of Hub SS3
4
 Hub SS5 - Self-powered USB3.0 Hub on port 1 of Hub SS4
5
6
 SS Low Power Drive on port 1 of Hub SS5
6
 SS Video Camera on port 2 of Hub SS5
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
5
 HS Drive on port 1 of Hub HS5
6
 Display Adapter on Port 3 of SS4
5
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
3
4
 FS Drive on port 4 of Hub FS3-1
4
 Keypad on port 2 of FS3-1
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
3
4
 FS Video Camera on port 1 of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
5.1
Host Inspection
Examine the Host Under Test and identify all USB connections.
o
Each and every USB port on the Host Under Test must be tested and pass all
required tests. The xHCI Interoperability Tests must be run separately for each USB
port on the Host Under Test. If the Host Under Test has an embedded hub, then the
tests must also be run for any exposed embedded hub ports.
Select a USB port of the Host Under Test to run the xHCI Interoperability Tests on.
5.2
1.
Host Interoperability Tests
xHCI Controller Driver Installation
When testing the first port:
Ensure that the USB Host System has a clean install of the OS and the OS is configured as
described in Section 1.2.1. Turn off the USB Host System and install the Host Under Test into
the USB Host System if it is not already integrated.
o Ensure that the SuperSpeed Interop Tree is not attached to the Host Under Test or
embedded hub.
Power on the USB Host System. The xHCI driver is installed with the initial install of the
Windows 8.1 OS.
When testing all other additional ports:
No driver install procedure should be necessary, as they use the driver installed for the first
selected port. Ensure that Driver Verifier has been configured as described in Section 1.2.1.
2.
o
Ensure that the SuperSpeed Interop Tree is not attached to the Host Under Test or
embedded hub.

Pass:
1. (The OS identifies and automatically installs the Host Under Test driver
OR
2. The vendor-recommended install procedure installs the Host Under Test driver)
AND
3. The Host Under Test driver is installed correctly and operates (no yellow exclamation point is displayed in
device manager)

Fail:
1. The Host Under Test driver does not install
OR
2. The Host Under Test driver is installed correctly but is non-operational (yellow exclamation point is
displayed in device manager)
Peripheral Enumeration and Driver Installation
When testing the first port:
Do not install any drivers or software for any device in the SuperSpeed Interop Tree prior to
attaching the SuperSpeed Interop Tree to the selected USB port under test.
Attach the SuperSpeed Interop Tree by connecting Hub SS1 into the selected USB port under
test.
If the Host Under Test has an embedded hub and the selected USB port under test is
an exposed embedded hub port, then unplug Hub SS3 and Hub SS4; re-plug Hub
SS4 directly into port one of Hub SS2.
For each device in the SuperSpeed Interop Tree follow the vendor-recommended install.
Ensure that all drivers listed for each device in the SuperSpeed Interop Tree match what is
currently being tested under Driver Verifier. To display the existing drivers being verified by
Driver Verifier:
o
o
o
Open the run box (press the Windows Key + R together).
Type the command “Verifier”.
Select “Display existing settings”
When testing all other additional ports:
Attach the SuperSpeed Interop Tree by connecting Hub SS1 into the selected USB port under
test.
If the Host Under Test has an embedded hub and the selected USB port under test is an
exposed embedded hub port then unplug Hub SS3 and Hub SS4; re-plug Hub SS4 directly
into port one of Hub SS2.
No install procedure should be necessary, as they use the software installed for the first
selected port.
3.

Pass:
1. All SuperSpeed Interop Tree devices enumerate
AND
2. All SuperSpeed Interop Tree devices drivers are installed either automatically or through the vendor
recommended install procedure
AND
3. All SuperSpeed Interop Tree devices do not require a reboot
AND
4. All SuperSpeed Interop Tree devices are correctly identified by Device Manager and no yellow
exclamation point is shown for any device
AND
5. (Software installs without any software crashes or a blue screen
OR
6. No software required)

Fail:
1. Any device cannot be installed because it requires driver installation or application software BEFORE the
device is ever plugged in
OR
2. Any device does not enumerate or blue screens during enumeration
OR
3. Any device requires reboot
OR
4. Any device is incorrectly identified by Device Manager or any device is flagged as not operational (yellow
exclamation point)
OR
5. Installation software crashes or causes a blue screen
Interoperability
o
Operate all the devices in the SuperSpeed Interop Tree.
o
Whenever the Host Interoperability Test Steps state to operate all of the devices in the
SuperSpeed Interop Tree, this involves operating the following steps concurrently:

Operate the microphone in the Video Cameras by speaking into the microphone and
viewing its input level

This can be found under Control Panel -> Hardware and Sound -> Sound under
the “Recording” tab.

View streaming video from the SS Video Camera

View streaming video from the FS Video Camera
Poor video quality may be seen when Driver Verifier is enabled. If there was poor
quality, continue testing with the Driver Verifier enabled for all Interoperability
steps. Repeat all Interoperability steps with Driver Verifier off. USB-IF will compare
Interoperability results with Driver Verifier Enabled and Disabled to determine
Pass/Fail for certification.
4.
Transfer a 30+ MB file from the SS Low Power Drive to the FS Drive

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter

Strike keys on the keypad

Move the mouse
o
Verify that all devices are operating concurrently. Verify the Device Speed using the
USBView utility.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests
o
5.

Run tests 1-7 as specified in Chapter 7.
Topology Change 1
o
Stop all SuperSpeed Interop Tree device operation! Close any software that is used for
any SuperSpeed Interop Tree device operation and close the “Recording” tab window.
o
Operate the following devices concurrently:

Operate the microphone(s)

View streaming video from the SS Video Camera

Transfer a 30+ MB file from the SS Low Power Drive to the FS Drive

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video from monitor and listen to audio attached to USB Display Adapter

Strike keys on the keypad
o
While operating the devices, detach the Hub FS3-2 from port 3 on Hub HS2-MTT.
o
Reattach Hub FS3-2 to port 2 on Hub HS3-STT as shown in Figure 5-3 and Figure 5-4.
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS
Cable
(5m)
X
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-3: Topology Change 1
SS Video
Camera
xHCI
SS Cable (3m)
SS Cable (3m)
SS
Cable
(3m)
Hub
SS2
Hub
SS4
HS Cable (5m)
HS
Cable
(5m)
Hub
SS1
HS
Cable
(5m)
SS Cable (3m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
X
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-4: Topology Change 1 (embedded hub)
6.
o
Verify that all three file transfers continue to take place.
o
Verify that the SS Video Camera and Headset continues to function.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
1. After the topology change the file transfers continued to take place
AND
2. After the topology change the SS Video Camera continues to function
AND
3. All SuperSpeed Interop Tree devices operate correctly

Fail:
1. After the topology change any file transfer was cancelled
OR
2. After the topology change the SS Video Camera stopped functioning
OR
3. One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests (N/A)
o
7.
Not necessary for this test procedure.
Topology Change 2
o
Stop all SuperSpeed Interop Tree device operation! Close any software that is used for
any SuperSpeed Interop Tree device operation and close the “Recording” tab window.
o
Operate the following devices concurrently:

View streaming video from the SS Video Camera

View streaming video from the HS Video Camera

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter

Move the mouse
o
While operating the devices, detach the Hub FS3-1 from port 2 on Hub HS2-MTT.
o
Reattach Hub FS3-1 to port 1 on Hub HS3-STT as shown in Figure 5-5 and Figure 5-6.
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
X
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-5: Topology Change 2
SS Video
Camera
xHCI
SS Cable (3m)
SS Cable (3m)
SS
Cable
(3m)
Hub
SS2
Hub
SS4
HS Cable (5m)
HS
Cable
(5m)
Hub
SS1
HS
Cable
(5m)
SS Cable (3m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
X
SS Video
Camera
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 5-6: Topology Change 2 (embedded hub)
o
Verify that both file transfers continue to take place.
o
Verify that the SS Video Camera, HS Video Camera, and mouse continue to function.
o
Operate the microphone(s).

If the microphones do not work, this is acceptable. The current configuration may
require more bandwidth than Hub HS3-STT can provide. The test setup must be
restored to a configuration that has enough bandwidth by following the steps below:
Detach Hub FS3-1 from port 1 on Hub HS3-STT and reattach the Hub FS3-1 back to
port 2 on Hub HS2-MTT. This should set the configuration back to what is displayed
in Figure 5-3 and Figure 5-4.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
1. After the topology change the file transfers continued to take place
AND
2. After the topology change the SS Video Camera, HS Video Camera, and mouse continue to function
AND
3. All SuperSpeed Interop Tree devices operate correctly

Fail:
1. After the topology change any file transfer was cancelled
OR
2. After the topology change the SS Video Camera, HS Video Camera, or mouse stopped functioning
OR
3.
8.
All Devices Tests (N/A)
o
9.
One or more SuperSpeed Interop Tree devices fail to operate correctly
Not necessary for this test procedure.
Active ExpressCard Detach (ExpressCard xHCI)
o
This test is only run if the Host Under Test is an ExpressCard host.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.
o
While operating the devices, detach the Host Under Test ExpressCard from the USB Host
System.
o
Reconnect the Host Under Test ExpressCard to the same ExpressCard slot in the USB
Host System.
o
Close any software that is used for any SuperSpeed Interop Tree device operation and
close the “Recording” tab window.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly

1.
Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
OR
System blue screens / locks up
2.
10. Interoperability without Driver Verifier
o
Run this test only if there was poor video or audio quality when operating all of the
devices in the SuperSpeed Interop Tree.
o
Disable Driver Verifier:

Open the run box (press the Windows Key + R together)

Type the command “Verifier”

Select “Delete Existing Settings” and press Finish. Press “Yes” and restart the
machine.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
11. Function Remote Wake
o Connect a function-remote-wake capable SuperSpeed device to one of the root ports.
o
Put the system into sleep
o
Wake up the system by the function-remote-wake interface on the SuperSpeed device

Pass:
The system wakes up normally.

Fail:
The system has any abnormal behaviors.
12. Tree Enumeration on Each Exposed Port
o
Plug in the interop tree to each exposed port of host under test, check all devices are
enumerated correctly.

Pass:
The system enumerates all devices

Fail:
Any devices in the tree cannot be enumerated.
13. Each Host Testing
o If the system has multiple xHCI hosts built in, tests 1-12 should be performed on each
host.
14. Exposed Port Testing
o Connect a SuperSpeed device other than a Hub to one of exposed ports of xHCI host
under test. Run tests 1-7 as specified in Chapter 7.
o Repeat this test for each root port of the host.

Pass:
All the tests 1-7 of Chapter 7 PASS

Fail:
If any of the tests 1-7 of Chapter 7 FAIL
5.3
Host U1/U2 Test Steps
o
o
o
o
o
o
o
o
Connect a USB 3.0 hub to an exposed host port.
Connect a KGD to a downstream hub port with a USB Protocol Analyzer between the
hub and device.
Trace USB traffic including idle device time and normal KGD operation.
Verify that the link successfully enters U1 or U2.
Verify that the hub correctly sends a deferred packet to the KGD and to the host.
Verify that the KGD correctly sends an ERDY after the deferred packet.
Verify that the host re-sends the packet with the deferred bit cleared.
Verify that the KGD completes the re-sent packet.

Pass:
1. Link successfully enters U1 or U2
AND
2. Link returns to U0 and the original packet that was sent during U1/U2 is successfully completed

Fail:
1. Link remains in U0
OR
2. Re-Sent packet does not complete correctly
5.4
Host LPM Tests
Download the MUTT Software Package from Microsoft. Double click and install the MSI file.
After the install finishes the contents of the package will most likely be found under
C:\Program Files\USBTest\
Choose either the x86 or the x64 folder depending upon the system OS. Inside the folder
select the tool labeled UsbLPM.
Selective Suspend must be disabled when using the Usb LPM Tool. Go to Control Panel ->
Power Options -> Change Plan Settings -> Change advanced power settings. Under “USB
settings” choose “USB selective suspend setting” and set it to “Disabled”.
1.
Inactivity U1/U2 Entry Test – Hub Only
Open the UsbLPM application
o
Configure the hub as shown in Figure 5-7 and attach it to xHCI port.
xHCI
Hub
SS1
Figure 5-7: Hub Only Topology
Let the hub remain inactive for a few seconds and observe whether it enters U1 or U2.
2.

Pass:
Hub enters U1 or U2

Fail:
Hub remains in U0
Inactivity U1/U2 Entry Test – Hub and U1/U2 Enabled Device
o
Without detaching hub from the host, attach a SuperSpeed, U1/U2 enabled device as
shown in Figure 5-8.
xHCI
Hub
SS1
SS1
U1/U2
Enabled
Figure 5-8: Hub and U1/U2 Enabled Device
Allow the devices to remain inactive. Observe the LPM tool, the device should enumerate
and both the host and the device should enter U1 or U2.
3.

Pass:
1. Both device and hub enter U1 or U2
OR
2. The hub enters U1 and the device enters U2

Fail:
1. Either the hub and/or device remain in U0
OR
2. The device enters U1 while the hub enters U2 or U3
OR
3. The device enters U2 while the hub enters U3
Inactivity U1/U2 Entry Test – Hub and U1/U2 Disabled Device
o
Without detaching hub from the host, attach a SuperSpeed, U1/U2 disabled device as
shown in Figure 5-9.
xHCI
Hub
SS1
SS1
U1/U2
Disabled
Figure 5-9: Hub and U1/U2 Disabled Device
Allow the devices to remain inactive. Observe the LPM tool, the device should enumerate
and the hub should not enter U1 or U2 (assuming device remains in U0).
4.

Pass:
Hub remains in U0 with device

Fail:
Hub enters U1, U2 or U3 while device remains in U0
Active LPM Test
The USB LPM Tool has an active mode where it can request the device and hub to enter U1
or U2 and report a pass/fail. Because this test does not necessarily exhaust all possibilities
during U1/U2 testing it should be run 10 times.
o
Attach the configuration shown in Figure 5-8 to the host.
o
In the Mode of operation box select the option “testing”.
o
Select the SuperSpeed hub from the list as shown in Figure 5-10.
o
Click the “Start” button on the right.
o
Observe the test report for failures or errors during the test cases.
o
Repeat this test 9 more consecutive times

Pass:
All 10 consecutive test cases report “pass”

Fail:
1 or more consecutive test cases reported a “fail” or “error”
Figure 5-10: Usb LPM Tool Interface
5.5
RTC PowerGates Test
The RTC PowerGates test is applicable ONLY on systems that can support Connected
Standby and have an embedded wireless device attached to the USB controller. If a system
cannot support this feature or does not have an embedded wireless device attached to the
USB controller than this test is not applicable.
1.
Test Setup
o
Install the application RTC PowerGates available from Microsoft on the DUT. (Note: User
Account Control will need to be enabled).
o
Add RTC PowerGates to one of the first 3 Lock Screen Apps on the DUT. Choose option
“Settings” in the right side tool menu. In the right side tools menu select “Change PC
Settings”. Choose one of the first 3 Lock Screen Apps and select “RTC PowerGates”.
o
Copy the server application to another internet enabled PC (server) and get the IPv4
address of that PC. This can be retrieved using the command “ipconfig” in the command
line.
o
Open the server application on the server PC
o
Run “RTC PowerGates” on the DUT and put in the IPv4 address of the server system
retrieved in the previous step and enter it into the “Server” field
2.
o
Click “Connect” on channel 1
o
On the server system select the connected system from the text box and click “Send”. If
everything is set up correctly this should cause the DUT to make an audible sound (be
sure volume is turned up)
Operation
Put the DUT into Connected Standby and click “Send” on the server PC multiple times over a
period of time. The DUT should respond with an audible sound each time. Note: it may take
several seconds for the DUT to respond in some cases.

Pass:
DUT responds with audible sound each time “Send” is clicked on the server PC

Fail:
DUT does not respond with an audible sound any time “Send” is clicked on the server PC
6 Compound Devices
A compound device is any device that contains a hub with at least one device or hub
permanently attached downstream. Because a compound device adds hubs to the tree it is
necessary to adjust test topologies so the maximum cascaded hub count does not exceed 5.
6.1
Determine Compound Device Configuration
Determine the following about a compound device:
o
Internal hub depth
o
Hub depth of any downstream ports
o
Peripheral number and types (if any)
6.2
1.
Peripheral Test Topology for Compound Devices
Compound Device Test Tree – Initial Topology
If the compound device contains only one hub, construct the tree as shown in Figure 6-1,
removing SS2. If the compound contains two hubs, construct the tree in accordance with Figure
6-2, removing both SS2 and SS3. In the case where a test system contains an embedded hub
replace SS1 with the embedded hub as shown in Figure 6-3 and Figure 6-4.
If a compound device has exposed ports, attach the SuperSpeed low-power drive to one of the
ports on the last hub tier of the compound device. Otherwise connect it to hub SS5.
xHCI
SS Cable (3m)
SS
Cable
(3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
Hub
HS2-MTT
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
Hub
HS3-STT
SS Video
Camera
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
DUT
Mouse
HS/FS
Camera
Figure 6-1: SuperSpeed Interop Tree with Compound Device
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
xHCI
DUT
SS Cable (3m)
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
Mouse
HS/FS
Drive
HS/FS
Camera
Keypad
Figure 6-2: SuperSpeed Interop Tree with Dual-Hub Compound Device
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
SS Cable (3m)
SS Cable (3m)
Hub
SS4
DUT
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
Hub
HS3-STT
SS Video
Camera
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-3: SuperSpeed Interop Tree with Compound Device – Embedded Hub
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
xHCI
DUT
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
Hub
SS4
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
Hub
HS3-STT
SS Video
Camera
SS Low
Power Drive
Hub
HS5
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-4: SuperSpeed Interop Tree with Compound Device (Dual-Hub) – Embedded Hub
2.
xHCI Controller Driver Installation
Ensure that the USB Host System has a clean install of the OS and the OS is configured as
described in Section 1.2.1. Turn off the USB Host System and install the xHCI controller into
the USB Host System if it is not already integrated.
o
Ensure that the SuperSpeed Interop Tree is not attached to the xHCI controller or
embedded hub.
Power on the USB Host System. One of three scenarios is acceptable for the USB Host System
to install the xHCI controller driver:
o
The OS identifies and automatically installs the xHCI controller driver.
o
The OS displays that it cannot find the driver for the xHCI controller. Follow the vendorrecommended install procedure to complete the driver install.
o
If the xHCI controller is already integrated into the USB Host System, then the OS
displays nothing, as it has already attempted install for the xHCI controller with the
initial install of the OS. Follow the vendor-recommended install procedure to complete
the driver install.

Pass:
1. (The OS identifies and automatically installs the xHCI controller driver
OR
2.
The vendor-recommended install procedure installs the xHCI controller driver)
AND
3. The xHCI controller driver is installed correctly and operates (no yellow exclamation point is displayed in
device manager)

3.
Fail:
1. The xHCI controller driver does not install
OR
2. The xHCI controller driver is installed correctly but is non-operational (yellow exclamation point is
displayed in device manager)
Peripheral Enumeration and Driver Installation
Do not install any drivers or software for any device in the SuperSpeed Interop Tree prior to
attaching the SuperSpeed Interop Tree to the xHCI controller.
Attach the SuperSpeed Interop Tree by connecting SS1 into any port on the xHCI controller.
o
If the xHCI controller has an embedded hub, then remove Hub SS1 and attach HS2-MTT
and SS4 into the embedded hub.
For each device in the SuperSpeed Interop Tree (including the DUT) follow the vendorrecommended install procedure. Ensure that all drivers listed for each device in the
SuperSpeed Interop Tree match what is currently being tested under Driver Verifier. To
display the existing drivers being verified by Driver Verifier:
o
o
o
Open the run box (press the Windows Key + R together).
Type the command “Verifier”.
Select “Display existing settings”

Pass:
1. All SuperSpeed Interop Tree devices enumerate
AND
2. All SuperSpeed Interop Tree devices drivers are installed either automatically or through the vendor
recommended install procedure
AND
3. All SuperSpeed Interop Tree devices do not require a reboot
AND
4. All SuperSpeed Interop Tree devices are correctly identified by Device Manager and no yellow
exclamation point is shown for any device
AND
5. (Software installs without any software crashes or a blue screen
OR
6. No software required)

Fail:
1. Any device cannot be installed because it requires driver installation or application software BEFORE the
device is ever plugged in
OR
2. Any device does not enumerate or blue screens during enumeration
OR
3. Any device requires a reboot
OR
4. Any device is incorrectly identified by Device Manager or any device is flagged as not operational (yellow
exclamation point)
OR
5. Installation software crashes or causes a blue screen
4.
Interoperability
o
Operate all the devices in the SuperSpeed Interop Tree.

Whenever the Compound Device Interoperability Test Steps state to operate all of
the devices in the SuperSpeed Interop Tree, this involves operating the following
steps concurrently:

Operate the microphone in the Video Cameras by speaking into the microphone
and viewing the input sound monitor

This can be found under Control Panel -> Hardware and Sound -> Sound
under the “Recording” tab

View streaming video from the SS Video Camera

View streaming video from the FS Video Camera
Poor video quality may be seen when Driver Verifier is enabled. If there was
poor quality, continue testing with the Driver Verifier enabled for all
Interoperability steps. Repeat all Interoperability steps with Driver Verifier
off. USB-IF will compare Interoperability results with Driver Verifier
Enabled and Disabled to determine Pass/Fail for certification.

Transfer a 30+ MB file from the SS Low Power Drive to the FS Drive

Transfer a 1+ GB file from the HS Drive to the SS Low Power Drive

Watch video and listen to audio from monitor attached to USB Display Adapter

Operate the Compound Device Under Test


If the DUT contains SS Mass Storage Device, then transfer a 2GB+file from
the SS Low Power Drive to the DUT and transfer a 1GB+file from the DUT to
the HS Drive
If the DUT does not have a Mass Storage Device, then ensure the operation
on the DUT overlaps over the period of time that other devices in the tree are
operating.

Strike keys on keypad

Move the mouse
o
Verify that all devices are operating concurrently. Verify the Device Speed using the
USBView utility.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
5.
All Devices Tests
o
6.
Run tests 1-7 as specified in Chapter 7.
Topology Change 1
o
Operate all the devices in the SuperSpeed Interop Tree except the Device Under Test.
o
While operating the devices, detach the Device Under Test from Hub SS5
o
While operating the devices, reattach the Device Under Test to port 4 on Hub HS5 as
shown in Figure 6-5 through Figure 6-12.
xHCI
SS Cable (3m)
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS4
Hub
SS5
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
DUT
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-5: SuperSpeed Interop Tree with Compound Device – Topology Change 1
xHCI
SS Cable (3m)
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
DUT
Hub
FS3-2
Hub
FS3-1
HS
Drive
Mouse
HS/FS
Drive
HS/FS
Camera
Keypad
Figure 6-6: SuperSpeed Interop Tree with Dual-Hub Compound Device – Topology Change 1
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
SS Cable (3m)
Hub
SS4
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
DUT
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-7: SuperSpeed Interop Tree with Compound Device – Embedded Hub – Topology
Change 1
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
Hub
SS4
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
DUT
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-8: SuperSpeed Interop Tree with Compound Device (Dual-Hub) – Embedded Hub –
Topology Change 1
7.
o
Verify that all devices except for the Device Under Test continue to operate concurrently.
o
Operate the Device Under Test.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
All Devices Tests
o
8.
Run tests 1-7 as specified in Chapter 7.
Topology Change 2 (For Low/Full-speed capable Compound USB Devices only)
o
Operate all the devices in the SuperSpeed Interop Tree except the Device Under Test.
o
While operating the devices, detach the Device Under Test from port 4 on Hub HS5.
o
While operating the devices, attach the Device Under Test to port 3 on Hub FS3-1 as
shown below in Figure 6-9 through Figure 6-12.
xHCI
SS Cable (3m)
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
HS
Drive
DUT
Mouse
HS/FS
Drive
HS/FS
Camera
Keypad
Figure 6-9: SuperSpeed Interop Tree with Compound Device – Topology Change 2
xHCI
SS Cable (3m)
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
HS
Cable
(5m)
Hub
SS3
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
SS
Display
Adapter
Hub
HS3-STT
SS Video
Camera
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
DUT
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-10: SuperSpeed Interop Tree with Dual-Hub Compound Device – Topology Change 2
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
SS Cable (3m)
Hub
SS4
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
SS Video
Camera
Hub
HS3-STT
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
HS
Drive
DUT
Mouse
HS/FS
Drive
HS/FS
Camera
Keypad
Figure 6-11: SuperSpeed Interop Tree with Compound Device – Embedded Hub – Topology
Change 2
xHCI
SS Cable (3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
Hub
SS3
Hub
SS4
Hub
SS5
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS
Display
Adapter
Hub
HS3-STT
SS Video
Camera
SS Low
Power Drive
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
DUT
HS/FS
Drive
Keypad
HS
Drive
If DUT has
exposed ports
connect SS Low
Power Drive to
DUT instead
Mouse
HS/FS
Camera
Figure 6-12: SuperSpeed Interop Tree with Compound Device (Dual-Hub) – Embedded Hub –
Topology Change 2
o
Verify that all devices except for the Device Under Test are continuing to operate
concurrently.
9.
o
Operate the Device Under Test.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
Interoperability without Driver Verifier
o
Run this test only if there was poor video or audio quality when operating all of the
devices in the SuperSpeed Interop Tree. Run all interoperability test steps including
topology change 1 and topology change 2.
o
Disable Driver Verifier:

Open the run box (press the Windows Key + R together)

Type the command “Verifier”

Select “Delete Existing Settings” and press Finish. Press “Yes” and restart the
machine.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.

Pass:
All SuperSpeed Interop Tree devices operate correctly. For certification purposes USB-IF will compare results
between Driver Verifier Enabled and Driver Verifier Disabled to determine Pass/Fail.

Fail:
One or more SuperSpeed Interop Tree devices fail to operate correctly
10. Function Wake
o
If the DUT supports function remote wake, it should have an interface for users to initiate
function wake. To run this test, operate all the devices in the SuperSpeed Interop Tree
o
While operating the devices, put the system to sleep by going to the Start menu, select
the arrow next to the Shut Down button, and then choose Sleep.
o
Initiate function wake from one of the functions on the device to wake the system up.
o
Upon resuming, verify that the file transfers continue without error.
o
Close any software that is used for any SuperSpeed Interop Tree device operation and
close the “Recording” tab window.
o
Operate all the devices in the SuperSpeed Interop Tree. Verify that all devices are
operating concurrently.
o
Repeat this test for all functions that support wake. (The “Device Summary” test of
Command Verifier 3.0 identifies all functions (interfaces) that support function wake.

1.
Pass:
System sleeps
AND
System resumes
AND
File transfers continue without error
AND
All devices can function after resuming
AND
All functions that advertise wake capability will wake the machine
2.
3.
4.
5.

1.
2.
3.
4.
5.
6.
Fail:
System does not sleep
OR
System does not resume
OR
System blue screens / locks up
OR
Any device cannot function after resuming
OR
File transfers do not continue after resuming
OR
Function that supports wake doesn’t wake machine
11. Root Port Testing
o
Connect DUT to one of root ports of xHCI host. Run tests 1-7 as specified in Chapter 7.

Pass:
All the tests 1-7 of Chapter 7 PASS

Fail:
If any of the tests 1-7 of Chapter 7 FAIL
6.3
Compound Devices with Exposed Hub Ports
If a compound device has exposed ports from its embedded hub(s) those ports must also be
tested with a variety of traffic types. This must be done in addition to the tests defined in section
6.2.
1.
Compound Device Test Tree
Testing a compound device as a hub is shown in Figure 6-13 through Figure 6-16. Construct the
correct configuration based on the type of DUT and test system available. This is a subset of the
tests required for a hub.
xHCI
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
SS Cable (3m)
DUT
Hub
SS3
Hub
SS2
DUT
SS1
SS Cable (3m)
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS5
Hub
SS4
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-13: SuperSpeed Interop Tree with Compound Device Having Exposed Hub Ports
xHCI
SS
Cable
(3m)
SS Cable (3m)
DUT
SS Cable (3m)
DUT
SS1
Hub
SS3
HS
Cable
(5m)
SS Cable (3m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS4
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-14: SuperSpeed Interop Tree with Compound Device (Dual-Hub) Having Exposed
Hub Ports
xHCI
SS
Cable
(3m)
SS Cable (3m)
SS Cable (3m)
DUT
DUT
SS1
Hub
SS3
SS Cable (3m)
HS
Cable
(5m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
Hub
SS4
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-15: SuperSpeed Interop Tree with Compound Device Having Exposed Hub Ports –
Embedded Hub
xHCI
SS
Cable
(3m)
SS Cable (3m)
DUT
DUT
SS1
Hub
SS4
SS Cable (3m)
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
HS
Cable
(5m)
Hub
SS5
SS
Display
Adapter
SS Low
Power Drive
Hub
HS3-STT
SS Video
Camera
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 6-16: SuperSpeed Interop Tree with Compound Device (Dual-Hub) Having Exposed
Hub Ports – Embedded Hub
o
For the above configuration run the tests described in sections 6.2.2 through 6.2.11.
o
Note: There are no topology changes for this test.
6.4
Compound Device Current Measurement
Devices operating at SuperSpeed are allowed to draw a maximum configured current of
900mA and unconfigured current of 150mA. Devices operating at High-speed or below may
draw a maximum configured current of 500mA and unconfigured current of 100mA. Devices
must report their maximum configured current draw and their power configuration as self or
bus powered to the host and must operate within the regions reported. Additionally any
device that is in the suspended state may draw no more than 2.5mA.
If device has external power, check whether it enumerates without it and if so then run tests
with device configured as bus-powered.
o
o
o
o
o
o
Install USB30CV from the USB-IF SuperSpeed Tools page.
Connect a SuperSpeed Current Measurement Fixture between DUT and xHCI host as
shown in Figure 6-17.
Set up a Multimeter to measure current drawn from device.
Run “Current Measurement [3.0 Devices]“ test in Command Verifier.
Read meter at each prompt.
Read the value of “Max Power Consumption” from the log.
o
o
o
o
o
o
Read device type from the log: bus-powered, self-powered or both.
Record following values:
 Bus, Both or Self-Powered
 The current in un-configured mode
 Current in configured mode
 Current in U0
 Current in U1
 Current in U2
 Current in U3
Reload the xHCI controller driver being used for Interop.
Operate the device
Record the highest measured current value
Repeat all steps again with device operating at High-speed by changing SuperSpeed
cable with High-speed cable (Note: U0, U1, U2 and U3 are not applicable in High-speed
mode) use CV tests labeled “Current Measurement Test [2.0 Devices]”
DUT
xHCI
Current Measurement
Fixture
Figure 6-17: Compound Device Current Measurement Topology

Pass:
1. Device reports Self-Powered and does not operate as Bus-Powered
OR
2. Device reports Both-Powered or Bus-Powered and can operate as Bus-Powered
AND
3. Max Power Consumption reported is 900mA or less when operating at SuperSpeed and 500mA or less
when operating at High-speed or Full-Speed
AND
4. Measured Unconfigured Current is 150mA or less when operating at SuperSpeed and 100mA or less when
operating at High-speed or Full-Speed
AND
5. Measured Current during device operation, U0, U1 and U2 is less than or equal to reported Max Power
Consumption
AND
6. Measured Current in U3 is less than or equal to 2.5mA and reported Max Power Consumption

Fail:
1. Device reports Self-Powered but is capable of enumerating as Bus-Powered
OR
2. Max Power Consumption reported is greater than 900mA when operating at SuperSpeed or greater than
500mA when operating at High-speed or Full-Speed
OR
3. Measured Unconfigured Current is greater than 150mA when operating at SuperSpeed or greater than
4.
5.
6.5
100mA when operating at High-speed or Full Speed
OR
Measured Current during device operation, U0, U1 or U2 is greater than reported Max Power
Consumption
OR
Measured Current in U3 is greater than 2.5mA or reported Max Power Consumption
Compound Device U1/U2 Test Steps
o
o
o
o
o
o
o
o
Connect a USB 3.0 hub to an exposed host port.
Connect a DUT to a downstream hub port with a USB Protocol Analyzer between the
hub and device.
Trace USB traffic including idle device time and normal DUT operation.
Verify that the link successfully enters U1 or U2.
Verify that the hub correctly sends a deferred packet to the DUT and to the host.
Verify that the DUT correctly sends an ERDY after the deferred packet.
Verify that the host re-sends the packet with the deferred bit cleared.
Verify that the DUT completes the re-sent packet.

Pass:
1. Link successfully enters U1 or U2
AND
2. Link returns to U0 and the original packet that was sent during U1/U2 is successfully completed

Fail:
1. Link remains in U0
OR
2. Re-Sent packet does not complete correctly
6.6
Compound Device LPM Tests
Download the MUTT Software Package from Microsoft. Double click and install the MSI file.
After the install finishes the contents of the package will most likely be found under
C:\Program Files\USBTest\
Choose either the x86 or the x64 folder depending upon the system OS. Inside the folder
select the tool labeled UsbLPM.
Selective Suspend must be disabled when using the Usb LPM Tool. Go to Control Panel ->
Power Options -> Change Plan Settings -> Change advanced power settings. Under “USB
settings” choose “USB selective suspend setting” and set it to “Disabled”.
Note: The hub is required to be in an equal or higher link state than any device(s) attached to
its downstream port(s). If at any time the hub goes to a lower link state than an attached
device the hub fails testing.
1.
Inactivity U1/U2 Entry Test – Compound Device Only
Open the Usb LPM Tool
o
Configure the Device Under Test as shown in Figure 3-10 and attach it to an xHCI port.
xHCI
DUT
DUT
Figure 6-18: Compound Device Only Topology
Let the device remain inactive for a few seconds and observe whether it enters U1 or U2.
2.

Pass:
1. Both internal device(s) and internal hub(s) enter U1 or U2
OR
2. The internal hub(s) enter U1 and the internal device(s) enter U2

Fail:
1. Either the internal hub(s) and/or internal device(s) remain in U0
OR
2. The internal device(s) enter U1 while the internal hub(s) enter U2 or U3
OR
3. The internal device(s) enter U2 while the internal hub(s) enter U3
Inactivity U1/U2 Entry Test – Compound Device and U1/U2 Enabled Device – Exposed
External Ports Only
This test is only applicable to Compound Devices that contain exposed ports.
o
o
o
Detach device from the host.
Attach a SuperSpeed, U1/U2 enabled device to one of the exposed downstream ports
Attach tree to the host as shown in Figure 3-11.
xHCI
DUT
HUT
SS1
U1/U2
Enabled
Figure 6-19: Compound Device and U1/U2 Enabled Device
Allow the devices to remain inactive. Observe the LPM tool, all devices should enumerate
and both the hub(s) and the device(s) should enter U1 or U2.

Pass:
1.
2.

3.
Both device(s) and internal hub(s) enter U1 or U2
OR
The internal hub(s) enter U1 and device(s) enter U2
Fail:
1. Either the internal hub(s) and/or devices remain in U0
OR
2. The device(s) enter U1 while the internal hub(s) enter U2 or U3
OR
3. The device(s) enter U2 while the internal hub(s) enter U3
Inactivity U1/U2 Entry Test – Compound Device and U1/U2 Disabled Device – Exposed
External Ports Only
This test is only applicable to Compound Devices that contain exposed ports.
o
o
o
Detach device from the host.
Attach a SuperSpeed, U1/U2 disabled device to one of the exposed downstream ports.
Attach tree to the host as shown in Figure 3-12.
xHCI
DUT
HUT
SS1
U1/U2
Disabled
Figure 6-20: Compound Device and U1/U2 Disabled Device
Allow the devices to remain inactive. Observe the LPM tool, the device should enumerate
and the hub should not enter U1 or U2 (assuming device remains in U0).
4.

Pass:
1. internal device(s) enter U1 or U2 and internal hub remains in U0 (external device stays in U0 as expected)

Fail:
1. The internal hub(s) enter U1, U2 or U3 while external device remains in U0
OR
2. The internal device(s) remain in U0
Active LPM Test
The USB LPM Tool has an active mode where it can request the device and hub to enter U1
or U2 and report a pass/fail. Because of a possible variance of behavior this test must be run
and pass 10 consecutive times.
o
Attach the configuration shown in Figure 6-19 to an available xHCI port.
o
In the Mode of operation box select the option “testing”.
o
Select the SuperSpeed hub from the list as shown in Figure 6-21.
o
Click the “Start” button on the right.
o
Observe the test report for failures or errors during the test cases.
o
Repeat this test 9 more consecutive times

Pass:
All 10 consecutive test cases report “pass”

Fail:
1 or more consecutive test cases reported a “fail” or “error”
Figure 6-21: Usb LPM Tool Interface
7 All Devices – xHCI Interoperability Test Steps
1.
Inactive Detach & Reattach
o
Stop all xHCI SuperSpeed Interoperability Tree device operation! Close any
software that is used for any xHCI Interoperability Tree device operation and close
the “Recording” tab window.
o
Detach the entire xHCI SuperSpeed Interoperability Tree from the selected port(s).
o
Reattach the entire xHCI SuperSpeed Interoperability Tree to the same selected
port(s) that it was detached from.
o
For Hub under Test, Detach and Reattach SS KGD connected to the downstream port
as an additional test. This test is in addition to the upstream port inactive
detach/reattach.
o
Operate all the devices in the xHCI SuperSpeed Interoperability Tree. Verify that all
devices are operating concurrently. Verify the Device Speed using the USBView
utility.

Pass:
All xHCI SuperSpeed Interoperability Tree devices operate correctly

Fail:
One or more xHCI SuperSpeed Interoperability Tree devices fail to operate correctly
2.
Active Sleep/Remote Wake – S3 Capable Systems Only
Note: Hub and Peripheral Test Systems are required to support this state

o
Operate all the devices in the xHCI SuperSpeed Interoperability Tree.
o
While operating the devices, use the Hybrid Sleep batch file to put the system into
sleep.
o
Wait 60 seconds then wake the system with the mouse on the SuperSpeed
Interoperability Tree.
o
Upon resuming verify file transfers resume without error and that no application
crashes. Note: if necessary it is acceptable to close and reopen the audio/video
application after resuming.
o
Operate all devices in the xHCI SuperSpeed Interoperability Tree. Verify that all
devices are operating concurrently. Verify the Device Speed using the USBView
utility.
Pass:
1. System sleeps
AND
2. System resumes
AND
3. Active operation continues without error

3.
Fail:
1. System does not sleep
OR
2. System does not resume
OR
3. System blue screens / locks up
OR
4. Any device is not functional or does not continue operation
OR
5. Any application freeze or crash
Active S4 Hibernation/Resume – S4 Capable Systems Only
Note: Hub and Peripheral Test Systems are required to support this state
4.
o
Operate all the devices in the xHCI SuperSpeed Interoperability Tree.
o
While operating the devices, use the Hibernate batch file to put the system into
hibernation. This will hibernate the system for 60 seconds and automatically resume
the system.
o
Upon resuming verify file transfers resume without error and that no application
crashes. Note: if necessary it is acceptable to close and reopen the audio/video
application after resuming.
o
Operate all devices in the xHCI SuperSpeed Interoperability Tree. Verify that all
devices are operating concurrently. Verify the Device Speed using the USBView
utility.

Pass:
1. System hibernates
AND
2. System resumes
AND
3. Active operation initiated in previous step continues without error

Fail:
1. System does not hibernate
OR
2. System does not resume
OR
3. System blue screens / locks up
OR
4. Any device is not functional or does not continue operation
OR
5. Any application freeze or crash
Active Connected Standby/Resume – Connected Standby Capable Systems Only
o
Operate all the devices in the xHCI SuperSpeed Interoperability Tree.
5.
o
While operating the devices, use the Connected Standby batch file to put the system
into hibernation. This will hibernate the system for 60 seconds and automatically
resume the system.
o
Upon resuming verify that the system entered into the Resiliency Phase (deepest
power saving phase of connected standby). This can be done by opening the log
generated by pwrtest.exe and examining it for the line “Entering Resiliency Phase”
o
If the system fails to enter the Resiliency Phase try again and let the system remain in
Connected Standby for a longer period of time.
o
Verify that file transfers resume without error and that no application crashes. Note:
if necessary it is acceptable to close and reopen the audio/video application after
resuming.
o
Operate all devices in the xHCI SuperSpeed Interoperability Tree. Verify that all
devices are operating concurrently. Verify the Device Speed using the USBView
utility.

Pass:
1. System enters Connected Standby
AND
2. System enters deepest power saving phase “Resiliency Phase”
AND
3. System Resumes
AND
4. Active operation initiated in previous step continues without error

Fail:
1. System does not enter Connected Standby
OR
2. System does not enter Resiliency Phase
OR
3. System does not resume
OR
4. System blue screens / locks up
OR
5. Any device is not functional or does not continue operation
OR
6. Any application freeze or crash
Warm boot
o
If there are file copying processes, let the finish and then close all of them.
o
Restart system.
o
After system reboots operate all the devices in the xHCI SuperSpeed Interoperability
Tree. Verify that all devices are operating concurrently. Verify the Device Speed
using the USBView utility.

Pass:
All xHCI SuperSpeed Interoperability Tree devices operate correctly

Fail:
One or more xHCI SuperSpeed Interoperability Tree devices fail to operate correctly
6.
Cold boot
o
If there are file copying processes, let the finish and then close all of them.
o
Turn off system with the ColdBoot.bat batch file. Turn off the External Power Supply
for the Host Controller (if applicable).
o
Turn PC and External Power Supply for the Host Controller back on.
o
After system boots operate all the devices in the xHCI SuperSpeed Interoperability
Tree. Verify that all devices are operating concurrently. Verify the Device Speed
using the USBView utility.

Pass:
All xHCI SuperSpeed Interoperability Tree devices operate correctly

Fail:
One or more xHCI SuperSpeed Interoperability Tree devices fail to operate correctly
7.
Hybrid boot
o
If there are file copying processes, let the finish and then close all of them.
o
Turn off system by double-clicking on the HybridBoot.bat file. Turn off the External
Power Supply for the Host Controller.
o
Turn PC and External Power Supply for the Host Controller back on.
o
After system boots operate all the devices in the xHCI SuperSpeed Interoperability
Tree. Verify that all devices are operating concurrently. Verify the Device Speed
using the USBView utility.

Pass:
All xHCI SuperSpeed Interoperability Tree devices operate correctly

Fail:
One or more xHCI SuperSpeed Interoperability Tree devices fail to operate correctly
USB Peripheral Interoperability
Peripheral Overall
PASS/FAIL
Peripheral Interoperability Tests
1.
xHCI Controller Driver Installation:
PASS/FAIL
2.
Peripheral Enumeration and Driver Installation:
PASS/FAIL
3.
Interoperability:
PASS/FAIL
4.
All Device Tests:
PASS/FAIL
1) Inactive Detach & Reattach:
PASS/FAIL
2) Active Sleep/Remote Wake:
PASS/FAIL
3) Active S4 Hibernation/Resume:
PASS/FAIL
4) Active Connected Standby/Resume
PASS/FAIL
5) Warm boot:
PASS/FAIL
6) Cold boot:
PASS/FAIL
7) Hybrid boot (Win8 Only)
PASS/FAIL
5.
Topology Change 1:
PASS/FAIL
6.
All Device Tests:
PASS/FAIL
8) Inactive Detach & Reattach:
PASS/FAIL
9) Active Sleep/Remote Wake:
PASS/FAIL
10) Active S4 Hibernation/Resume:
PASS/FAIL
11) Warm boot:
PASS/FAIL
12) Cold boot:
PASS/FAIL
13) Hybrid boot (Win8 Only)
PASS/FAIL
7.
Topology Change 2:
PASS/FAIL/NA
8.
All Device Tests:
PASS/FAIL/NA
14) Inactive Detach & Reattach:
PASS/FAIL
9.
15) Active Sleep/Remote Wake:
PASS/FAIL
16) Active S4 Hibernation/Resume:
PASS/FAIL
17) Warm boot:
PASS/FAIL
18) Cold boot:
PASS/FAIL
19) Hybrid boot (Win8 Only)
PASS/FAIL
Interoperability without Driver Verifier:
PASS/FAIL/NA
10. Current Measurement:
PASS/FAIL
11. Function Wake:
PASS/FAIL
12. Root Port Testing
PASS/FAIL
13. U1/U2 Test Steps
PASS/FAIL
14. LPM Tests
PASS/FAIL
USB Self-Powered Hub Interoperability
Self-Powered Hub Overall
PASS/FAIL
Self-Powered Hub Interoperability Tests
1.
xHCI Controller Driver Installation:
PASS/FAIL
2.
Peripheral Enumeration and Driver Installation:
PASS/FAIL
3.
Interoperability:
PASS/FAIL
4.
All Device Tests:
PASS/FAIL
1) Inactive Detach & Reattach:
PASS/FAIL
2) Active Sleep/Remote Wake:
PASS/FAIL
3) Active S4 Hibernation/Resume:
PASS/FAIL
4) Warm boot:
PASS/FAIL
5) Cold boot:
PASS/FAIL
6) Hybrid boot (Win8 Only):
PASS/FAIL
5.
Topology Change 1:
PASS/FAIL
6.
All Device Tests:
PASS/FAIL
1) Inactive Detach & Reattach:
PASS/FAIL
2) Active Sleep/Remote Wake:
PASS/FAIL
3) Active S4 Hibernation/Resume:
PASS/FAIL
4) Warm boot:
PASS/FAIL
5) Cold boot:
PASS/FAIL
6) Hybrid boot (Win8 Only):
PASS/FAIL
7.
Topology Change 2:
PASS/FAIL
8.
All Device Tests:
PASS/FAIL
1) Inactive Detach & Reattach:
PASS/FAIL
2) Active Sleep/Remote Wake:
PASS/FAIL
3) Active S4 Hibernation/Resume:
PASS/FAIL
9.
4) Warm boot:
PASS/FAIL
5) Cold boot:
PASS/FAIL
6) Hybrid boot (Win8 Only):
PASS/FAIL
Interoperability without Driver Verifier:
PASS/FAIL/NA
10. Function Wake:
PASS/FAIL
11. Current Measurement Tests:
PASS/FAIL
12. U1/U2 Tests:
PASS/FAIL
13. LPM Tests:
PASS/FAIL
xHCI Interoperability Test Results
xHCI Overall
PASS/FAIL
xHCI Interoperability Tests
1.
xHCI Controller Driver Installation:
PASS/FAIL
2.
Peripheral Enumeration and Driver Installation:
PASS/FAIL
3.
Interoperability:
PASS/FAIL
4.
All Device Tests (If Applicable):
PASS/FAIL
1.
Inactive Detach & Reattach:
PASS/FAIL
2.
Active Sleep/Remote Wake:
PASS/FAIL
3.
Active S4 Hibernation/Resume:
PASS/FAIL
4.
Warm boot:
PASS/FAIL
5.
Cold boot:
PASS/FAIL
6.
Hybrid boot (Win8 Only):
PASS/FAIL
5.
Topology Change 1:
PASS/FAIL
6.
All Device Tests:
PASS/FAIL
7.
Topology Change 2:
PASS/FAIL
8.
All Device Tests:
PASS/FAIL
9.
Active Express Card Detach (Express Card xHCI):
PASS/FAIL/NA
10. Interoperability without Driver Verifier:
PASS/FAIL/NA
11. Function Wake:
PASS/FAIL
12. Tree Enumeration on Each Exposed Port:
PASS/FAIL
13. Each Host Testing:
PASS/FAIL
14. Exposed Port Testing:
PASS/FAIL
15. Host U1/U2 Modes:
PASS/FAIL
16. LPM Tests
PASS/FAIL
8 Appendix A – Driver Verifier
xHCI Interoperability testing should be tested with driver verifier enabled in order to help catch
problems that may arise during testing. A pre-defined list of drivers has been developed by the
USB-IF for both Windows 7 and Windows 8.1. Please choose the correct drivers to verify based
on your operating system and then put these drivers into Driver Verifier as described in section
1.2.1.
8.1
List of Drivers for Windows 7:
Flag Setting: verifier /flags 0xffb
cdrom.sys
disk.sys
hidclass.sys
hidparse.sys
hidusb.sys
kbdclass.sys
kbdhid.sys
mouclass.sys
mouhid.sys
partmgr.sys
portcls.sys
usbccgp.sys
usbd.sys
usbehci.sys
usbhub.sys
usbohci.sys
usbport.sys
usbprint.sys
usbstor.sys
usbuhci.sys
usbvideo.sys
vx3000.sys
Any class or device-specific drivers used by a Device Under Test
Fresco Logic Host Drivers:
Flxhcic.sys
Flxhcih.sys
Please ensure that the host driver names are correct for the host that is being used in the
xHCI SuperSpeed Interoperability Tree.
8.2
List of Drivers for Windows 8.1:
Flag Setting: Verifier /flags 0x2099B /driver
bthusb.sys
hidclass.sys
hidparse.sys
hidusb.sys
kbdclass.sys
kbdhid.sys
mouclass.sys
mouhid.sys
uaspstor.sys
ucx01000.sys
usbaudio.sys
usbccgp.sys
usbd.sys
usbehci.sys
usbhub.sys
usbhub3.sys
usbohci.sys
usbport.sys
usbprint.sys
usbscan.sys
usbstor.sys
usbuhci.sys
usbvideo.sys
usbxhci.sys
winusb.sys
wmbclass.sys
Add Display Adapter Driver’s
Any class or device-specific drivers used by a Device Under Test
9 Appendix B – Modified Interop Trees
This appendix details temporary changes to this document. Unless noted here, all steps must be
followed as described earlier in this document. All steps to verify interoperability, including
driver verifier usage, function remote wake operation, current measurement, etc., must be
followed as described in the main document. This appendix is only intended as a brief summary
of testing changes required by lack of approved devices for the final interoperability tree.
USB Peripheral Interoperability Test Steps
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
SS Cable (3m)
Hub
SS3
SS Cable (3m)
Hub
SS4
Hub
SS5
SS Cable (3m)
HS
Cable
(5m)
HS Cable (5m)
DUT
Hub
HS2-MTT
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Headset
Keypad
Mouse
HS/FS
Camera
Figure 9-1: Modified Device Interoperability Interim Tree
Modified tree:
Tier Device
1
 Hub SS1– Self-powered USB3.0 Hub at Root Port
 Hub SS2 - Self-powered USB3.0 Hub on port 1 of Hub SS1
2
 Hub SS3 - Self-powered USB3.0 Hub on port 1 of Hub SS2
3
 Hub SS4 - Self-powered USB3.0 Hub on port 1 of Hub SS3
4
5
 Hub SS5– Self-powered USB3.0 Hub on port 1 of Hub SS4
 DUT on port 1 of Hub SS5
6
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
5
 HS Drive on port 1 of Hub HS5
6
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
3
4
 Headset on port 1 of Hub FS3-1
4
 FS Drive on port 4 of Hub FS3-1
4
 Keypad on port 2 of FS3-1
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
3
4
 FS Video Camera on port 1 of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
Chapter 2
a. Testing of DUT at Root Port
o
o
o
o
Connect DUT to a port of xHCI controller
Operate all devices at root port
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
b. Test of DUT behind SS hub
o
o
o
o
o
o
Disconnect all devices from xHCI controller
Attach DUT to port 1 of Hub SS5 in the modified tree
Attach modified tree to xHCI controller
Operate all devices in tree as described in main document
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
c.
o
o
o
o
o
Test of DUT behind HS hub
Unplug DUT from SS5
Plug DUT into port 4 of HS Hub of HS5
Operate all devices in tree as described in main document
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
d. Test of DUT behind FS hub
o
o
o
o
Unplug DUT from HS5
Plug DUT into port 3 of FS3-1
Operate all devices in tree as described in main document
Use same pass/fail criteria as used in main document
USB Self-Powered Hub Interoperability Test Steps
Chapter 3
xHCI
SS
Cable
(3m)
SS Cable (3m)
HUT
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HUT
SS5
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
SS Low
Power Drive
Hub
HS3-STT
Hub
HS5
HS
Cable
(5m)
HS Cable (5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 9-2: Modified Hub Interoperability Interim Tree
HS Video
Camera
Tier Device
1
 Hub SS1– Self-powered USB3.0 Hub Under Test (HUT) at Root Port
2
 Hub SS2 - Self-powered USB3.0 KGH on port 1 of Hub SS1
 Hub SS3 - Self-powered USB3.0 KGH on port 1 of Hub SS2
3
4
 Hub SS4 - Self-powered USB3.0 KGH on port 1 of Hub SS3
5
 Hub SS5– Self-powered USB3.0 Hub Under Test (HUT) on port 1 of
Hub SS4
6
 SS Low Power Drive on port 1 of Hub SS5
6
 HS Video Camera on port 2 of Hub SS5
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
5
 HS Drive on port 1 of Hub HS5
6
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
3
4
 Headset on port 1 of Hub FS3-1
4
 FS Drive on port 4 of Hub FS3-1
4
 Keypad on port 2 of FS3-1
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
3
4
 FS Video Camera on port 1 of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
a. DS port test
o
o
o
Connect 2 KGD’s to DS port’s of 1 HUT. Connect upstream port of HUT to the
XHCI Host
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
b. Interop tree test
o
o
o
o
o
Connect HUTs as shown in Figure 9-2* (Note use of 5 hubs)
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
Do topology changes as specified in Chapter 3
Do 5 HUT Interop, by replacing Hub SS2 with HUT SS2, Hub SS3 with HUT SS3,
and Hub SS4 with HUT SS4. Run tests 1-7 as specified in Chapter 7. Do
topology changes as specified in Chapter3.
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
Hub
SS2
SS Cable (3m)
SS Cable (3m)
Hub
SS3
SS Cable (3m)
Hub
SS4
Hub
SS5
SS
Display
Adapter
Figure 9-3: Modified Hub Interoperability Interim Tree – Display Device
Tier Device
1
2
 Hub SS1– Self-powered USB3.0 Hub Under Test (HUT) at Root Port
 Hub SS2 - Self-powered USB3.0 Hub Under Test (HUT) on port 1 of Hub SS1
 Hub SS3 - Self-powered USB3.0 Hub Under Test (HUT) on port 1 of Hub SS2
3
4
 Hub SS4 - Self-powered USB3.0 Hub Under Test (HUT) on port 1 of Hub
SS3
5
 Hub SS5– Self-powered USB3.0 Hub Under Test (HUT) on port 1 of
Hub SS4
5
 SS Display Adapter– USB Video Display Adapter on port 4 of SS5
Interop 5 Deep HUT plus SS Isoch device test
o
o
o
Connect HUTs as shown in Figure 9-3 (Note use of 5 hubs)
Run tests 1-7 as specified in Chapter 7
Use same pass/fail criteria as used in main document
USB Host Interoperability Test Steps
Chapter 5
xHCI
SS
Cable
(3m)
SS Cable (3m)
Hub
SS1
SS Cable (3m)
Hub
SS2
HS
Cable
(5m)
Hub
SS3
SS Cable (3m)
Hub
SS4
HS
Cable
(5m)
HS Cable (5m)
Hub
HS2-MTT
SS Cable (3m)
Hub
SS5
SS
Display
Adapter
SS Low
Power
Drive/KGD
Hub
HS3-STT
Hub
HS5
HS Cable (5m)
HS
Cable
(5m)
Hub
FS3-2
Hub
FS3-1
HS
Drive
HS/FS
Drive
Keypad
Mouse
HS/FS
Camera
Figure 9-4: Modified Host Interoperability Interim Tree
HS Video
Camera
Tier Device
1
2
 Hub SS1– Self-powered USB3.0 Hub attached to the xHCI controller under test
 Hub SS2 - Self-powered USB3.0 Hub on port 1 of Hub SS1
 Hub SS3 - Self-powered USB3.0 Hub on port 1 of Hub SS2
3
 Hub SS4 - Self-powered USB3.0 Hub on port 1 of Hub SS3
4
 Hub SS5 - Self-powered USB3.0 Hub on port 1 of Hub SS4
5
6
 SS Low Power Drive/KGD on port 1 of Hub SS5
6
 HS Video Camera on port 2 of Hub SS5
 Hub HS5 - Self-powered high-speed Hub on port 2 of Hub SS4
5
 HS Drive on port 1 of Hub HS5
6
 Display Adapter on Port 3 of SS4
5
2
 Hub HS2-MTT - Self-powered high-speed Hub with multiple transaction translators
on port 2 of Hub SS1
3
 Hub HS3-STT - Self-powered high-speed Hub with a single transaction
translator on port 1 of Hub HS2-MTT
 Hub FS3-1 – Full-Speed Hub on port 2 of Hub HS2-MTT
3
4
 FS Drive on port 4 of Hub FS3-1
4
 Keypad on port 2 of FS3-1
 Hub FS3-2 - Full-Speed Hub on port 3 of Hub HS2-MTT
3
4
 FS Video Camera on port 1 of Hub FS3-2
4
 Mouse on port 2 of Hub FS3-2
c. Root port test.
o
o
o
o
Operate one KGD at root port
Run tests 1-7 as specified in Chapter 7
Repeat the test with each KGD
Use same pass/fail criteria as used in main document
d. Interoperability with Modified Tree
o
o
o
o
o
o
o
e.
o
o
Remove all devices from xHCI controller
Attach one KGD to hub SS5 of Modified Tree. Refer to Figure 8-3
Attach Modified Tree to one xHCI controller port
Operate all devices in tree as described in main document
Run tests 1-7 as specified in Chapter 7
Do Topology Changes 1 and 2 as described in the main document
Use same pass/fail criteria as used in main document
Root port enumeration with Modified Tree
Attach the tree to the other root ports
Check all devices are enumerated correctly
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising