USB Hub Exposed Port Test
This test verifies that a USB 3.0 hub adheres to Section 10.1 of the USB 3.0 Specification.
As per the specification, a USB 3.0 hub has two hub units: a SuperSpeed hub and a companion high-speed hub to handle USB 3.0 and 2.0 traffic, respectively. Ports on both of these hubs make connectors or physical ports. In this test, those ports are called exposed ports. This test checks the port mapping of SuperSpeed and high-speed hub units.
This test applies to USB 3.0 hubs only, and automatically passes for non-SuperSpeed-capable hubs.
In Windows 8.1, this test runs in two modes: Legacy and Modern. The mode is selected by using the Parameters option. In the Legacy mode, the test is manual. You can configure the hubs before or after you start the test. In the Modern mode, the test is automated and you must configure the required topologies before you start the test.
Test details
Associated requirements |
Device.Connectivity.UsbHub.IdentifyNumOfUserAccessiblePorts Device.Connectivity.UsbHub.MapPortsPerUsb3Specification |
Platforms |
Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2 |
Expected run time |
~5 minutes |
Categories |
Certification Functional |
Type |
Manual |
Running the test
Hardware list
The external USB 3.0 hub to test.
In the Legacy mode, you need at least one additional USB-IF compliant external USB 3.0 hubs. In the Modern mode, you need n additional USB 3.0 hubs, where n is the total count of connectors on the hub. In this topic, these hubs are also called second-tier hubs.
One eXtensible Host Controller Interface (xHCI) controller on the test computer.
SuperSpeed-capable USB cables.
Before you run the test
Before you run the test, complete the test setup as described in the test requirements: USB Device.Connectivity Testing Prerequisites.
Verify that the container IDs of the USB 3.0 and 2.0 hub units match. You can verify the container IDs in Device Manager, as shown here:
Art placeholder
The order of port numbers of the two hub units must match. For example, if the USB 3.0 hub’s port numbers are 1, 2, 3, and 4, the USB 2.0 hub’s port numbers must also be 1, 2, 3, and 4.
The ports of USB 3.0 and 2.0 hubs that form a connector on the entire hub, must match. For example, if a USB 3.0 hub has four connectors and each connector has ports from each unit, the port numbers for a connector must be [1, 1] or [2, 2], and so on. Port number combination of [1, 2] is invalid.
Required hub configuration
The required hub configuration is shown in the following figure:
Art placeholder
How to run the test – Legacy mode
On the Windows Hardware Certification Kit (Windows HCK) Controller, open Windows HCK Studio and load the project.
On the target computer, connect the USB 3.0 hub to test, to a root hub port of a USB 3.0 host controller.
On the Windows HCK Controller, on the Selection tab, select Device manager and check the box for the hub to test from the list.
On the Windows HCK Controller, click the Tests tab, select USB Hub Exposed Port Test, and click Run Selected.
In the Parameters window, enter Legacy as the Testmode value.
Start the test.
The target computer might restart. On the test computer, Administrator: Windows PowerShell and USB device viewer windows will open.
Connect the second-tier hub to a downstream connector of the hub under test. In USB device viewer, verify that the hub enumerates as Generic SuperSpeed USB Hub under SuperSpeed ports. If you have n hubs for n connectors, connect all hubs at the same time. Make sure that all hubs are detected on all connectors. Do not close the test UI, or, the test will fail.
After all second-tier hubs are detected, the UI will close automatically. If it does not, close the test UI.
Read the test results on the Windows HCK Controller.
How to run the test – Modern mode
On the Windows HCK Controller, open Windows HCK Studio and load the project.
On the target computer, connect the USB 3.0 hub to test, to a root hub port of a USB 3.0 host controller.
Connect all second-tier hubs to downstream connectors of the USB 3.0 hub under test.
On the Windows HCK Controller, on the Selection tab, select Device manager and check the box for the hub to test from the list.
On the Windows HCK Controller, click the Tests tab, select USB Hub Exposed Port Test, and click Run Selected.
In the Parameters window, enter Modern as the Testmode value.
Start the test.
On the target computer a command prompt window opens; however, this mode requires no user interaction.
After the test completes, read the test results on the Windows HCK Controller.
Troubleshooting
For troubleshooting information, see Troubleshooting Device.Connectivity Testing.
If all second-tier hubs are attached to each port and the test UI remains on the screen, exit the window and examine the test logs. If the logs indicate that a USB 3.0 hub was not enumerated on the connectors of the USB 3.0 hub under test, it might show the following error strings:
| Error string | Description |
|---|---|
Device under test is missing from system. |
The USB 3.0 hub under test was removed after the test was started, but before the test ran on the target computer. |
No companion found! Port # is super speed, but was not mapped to a companion port. |
The USB 3.0 hub under test is not correctly implemented. The hub has a SuperSpeed hub unit but the companion hub was not detected. |
Port # is unmapped. |
A USB 3.0 hub was detected on the downstream connector, but a high-speed unit of that hub was not detected. |
Port # is reported as user removable, but no device was found. Please attach a device and rerun the test. |
One or more downstream connectors was missing hub(s). Re-run the test and ensure that the second-tier hub(s) are attached to every exposed port of the hub under test. |
Container ID: Fail. |
The SuperSpeed hub under test or second-tier hub(s) in use are not correctly implemented. The hub must properly implement the container IDs so that the SuperSpeed and high speed components share the same container ID. Confirm the container ID implementation of the secondary hub by examining the device property in Device Manager. |
More information
Command syntax
| Parameter | Description |
|---|---|
TestMode |
String that indicates whether the test runs in manual or automated mode. Modern: Uses WDTF to check USB port connections. The test runs automatically. Default value. Legacy: Uses USB Device Viewer to check USB port connections. The test runs in manual mode. |
Related topics