Debug Capability Test (Logo)

This test measures the ability of a test computer to support debug operations using an xHCI controller, EHCI controller, serial port, 1394 controller, or a network adapter. The test validates that at least one debug port is available.

Test details

Associated requirements

System.Fundamentals.DebugPort.SystemExposesDebugInterface

See the system 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

~20 minutes

Categories

Basic Certification Functional

Type

Manual

 

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 HCK prerequisites and must be included in the same computer pool. For more information, see Windows HCK 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.

Important  

You must have a cable that is appropriate for the debug transport that is being verified.

 

Troubleshooting

For troubleshooting information, see Troubleshooting the Windows HCK Environment.

This test returns Pass or Fail. To review test details, review the test log from HCK Studio.

More information

Command syntax

 In the Parameters window Transport field, enter one transport type (NET, 1394, USB, or Serial). Based on the transport you entered, you must provide the following additional parameters.

Transport type Required parameters Comments

NET

NetHostIP

You must specify a Host IP. If there's more than one 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 displayed in the device's properties window in Device Manager.

1394

1394Channel

Default is 1. If there's more than one controller on the SUT computer, you must specify a BusParams value. Enter Busparam as b.d.f where b, d, and f are the bus number, device number, and function displayed in the device's properties window in Device Manager.

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 cable must be connected to Port 1 of the controller. You can use the UsbView tool to identify Port 1. USBView is included in the WDK.

 

Serial

Not required

Default values are sufficient. If necessary, adjust any serial parameter as needed (prefix Serial_).

 

 

 

Send comments about this topic to Microsoft