Determine the bitness (32-bit or 64-bit) of Windows running on the host computer.

Connect a USB 3.0 debug cable to the USB 3.0 ports that you've chosen for debugging on the host and target computers.Start a debugging session for the first time When you finish using the xHCI host controller for debugging, re-enable selective suspend for the xHCI host controller. If there's a Power Management tab, open the tab, and clear the Allow the computer to turn off this device to save power check box.

Right click the node, and choose Properties. In Device Manager, navigate to the node for the root hub of the xHCI host controller. If there's a Power Management tab, open the tab, and clear the Allow the computer to turn off this device to save power checkbox. Right-click the node, and choose Properties. In Device Manager, navigate to the node for the xHCI host controller. To avoid these problems, disable selective suspend for the xHCI host controller, and its root hub, that you're using for debugging.

In some cases, power transitions can interfere with debugging over USB 3.0. Look for an indication that a port on the host controller supports debugging. In UsbView, expand the nodes of the xHCI host controllers. In UsbView, locate all of the xHCI host controllers. The UsbView tool is included in Debugging Tools for Windows. On the target computer, launch the UsbView tool. On the target computer, an xHCI (USB 3.0) host controller that supports debugging.On the host computer, an xHCI (USB 3.0) host controller.A USB 3.0 debug cable, which is an A-A crossover cable that has two male type-A plugs and no Vbus connection.The computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer.ĭebugging over a USB 3.0 cable requires the following hardware: This article describes how to manually set up USB 3.0 debugging. Debugging Tools for Windows supports kernel-mode debugging over a USB 3.0 cable.

Usb debugging windows 10 how to turn on