xHCI Debug Capability Compliance (Logo)

  • Article

This test measures the ability of a test computer to support debug operations using an xHCI controller.

Test details

   
Specifications
  • System.Fundamentals.DebugPort.USB.SystemExposesDebugInterfaceUsb
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 15
Category Development
Timeout (in minutes) 900
Requires reboot false
Requires special configuration true
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

To complete this debug test, you must configure two computers. The computer that you are trying to certify is the System under Test (SUT). The second computer is the Host on which the Windows debugger will run. These computers must meet the Windows HLK prerequisites and must be included in the same computer pool. For more information, see Windows HLK Prerequisites. If the device being tested is an XHCI controller, an XHCI controller must be included in both computers. If the XHCI controller in the SUT has any user-accessible ports, the controller must have debug capability.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

If the test will not run, enable file sharing on the host computer (second computer) and try again.

For troubleshooting information, see Troubleshooting Bus Controller Testing.

This test returns Pass or Fail. To review test details, review the test log from Windows Hardware Lab Kit (Windows HLK) Studio.

More information

Command syntax

In the Parameters window Transport field, enter USB. Provide the following additional parameters.

Transport type Required parameters Comments

USB

UsbTargetName

Default is default. If there's more than one USB host controller on the SUT computer, you must specify a BusParams value. Enter Busparams as b.d.f where b, d, and f are the bus number, device number, and function number of the USB host controller that you are using for debugging. These numbers are displayed in the USB host controller's Properties window in Device Manager.

Important  

If you are using an EHCI host controller on the SUT computer, the debug cable must be connected to Port 1. You can use the UsbView tool to identify Port 1. USBView is included in the WDK.

 

 

Parameters

Parameter name Parameter description
AccessiblePorts Please enter zero or one for the number of externally accessible USB3 ports
BusParams For a PCI-enumerated controller, please enter bus params as b.d.f where b, d, and f are the bus number, device number, and function displayed in the relevant device manager properties page. For an ACPI-enumerated controller, please enter a single integer.