USB Exposed Port Controller Test

  • Article

This manual test validates that USB exposed connectors support SuperSpeed, High, Full and Low Speed USB devices routed through its xHCI controller. The test also validates the port mapping of the high speed and SuperSpeed ports in each connector.

Test details

Associated requirements

Device.BusController.UsbController.SuperSpeedConnectorsSupportHighFullLow Device.BusController.UsbController.TestedUsingMicrosoftUsbStack Device.BusController.UsbController.XhciAddInCardsMapPortsConsistently Device.BusController.UsbController.XhciAddInCardsReportInternalDevices Device.BusController.UsbController.XhciVersionCompliant

See the device hardware requirements.

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

Before you run the test, complete the test setup as described in the test requirements: USB Bus Controller Testing Prerequisites.

A USB 3.0 Hub must be attached to each exposed connector of the xHCI controller. In addition to the USB 3.0 Hub, a low speed and full speed device must be attached to each exposed connector of the xHCI controller.

This is a manual test: the devices must be moved between each exposed connector of the USB host controller under test. Please allow several seconds for the device to fully enumerate on each connector before removing the device. The devices may be connected in any sequence as long as each device (low speed, full speed, and USB 3.0 hub) is plugged into each exposed connector at least once. You may use the device tree in the test UI to validate the device enumeration in for each device and connector. Once you have completed each step on each connector the test will automatically close.

  • We recommend using USB-IF certified hubs and low, full speed devices. For example, the Texas Instruments SuperSpeed USB 3.0 Hub reference design board (TUSB8040EVM) which can be used to evaluate system compatibility (https://go.microsoft.com/fwlink/p/?linkid=248509).

Troubleshooting

For troubleshooting information, see Troubleshooting Bus Controller Testing.

If you have attached each required device to each exposed connector and the test has not automatically closed, you must manual exit the test UI and examine the test logs in the WHCK studio. The logs will detail which devices were correctly enumerated and which devices were not. If a device failed to enumerate on the USB host controller under test, it will require further investigation. Re-run the test and explore the device tree in the UI to validate the failing test case. Manually check device responsiveness and functionality on the failing port as well.

If the USB 3.0 hub (port mapping) step of the test is failing it may be due to an improperly implemented hub. The container ID's of the high speed and SuperSpeed portion of the test hub must match in order for the test to validate host controller port mapping. Please see the hardware requirements section of the USB Host Controller Prerequisites for more information on a suitable USB 3.0 hub.

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 show check USB port connections. The test runs in manual mode.

 

 

 

Send comments about this topic to Microsoft