- #USB XHCI COMPLIANT HOST CONTROLLER CODE 43 SERIAL#
- #USB XHCI COMPLIANT HOST CONTROLLER CODE 43 DRIVER#
One way to do reboot the PC, is to use the shutdown -r -t 0 command from an administrator's command prompt.Īfter the target PC restarts, the debugger should connect automatically. Once the debugger is connected, reboot the target computer. Kd /k usb:targetname= TargetName Reboot the target computer On the host computer, open a Command Prompt window and enter the following command, where TargetName is the target name you created when you set up the target computer: Windbg /k usb:targetname= TargetName Using KD
You can also start a session with WinDbg by entering the following command in a Command Prompt window, where TargetName is the target name you created when you set up the target computer: Enter the target name that you created when you set up the target computer. In the Kernel Debugging dialog box, open the USB tab. Starting a Debugging Session Using WinDbg
#USB XHCI COMPLIANT HOST CONTROLLER CODE 43 DRIVER#
After the USB debug driver is installed, you can use either the 32-bit or 64-bit version of WinDbg for subsequent debugging sessions. This is why it is important to match the bitness of WinDbg to the bitness of Windows. Click OK.Īt this point, the USB debug driver gets installed on the host computer.
#USB XHCI COMPLIANT HOST CONTROLLER CODE 43 SERIAL#
Connect a Universal Serial Bus (USB) 3.0 debug cable to the USB 3.0 ports that you have chosen for debugging on the host and target computers.Starting a Debugging Session for the First Time When you have finished using the xHCI host controller for debugging, re-enable selective suspend for the xHCI host controller. If there is 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. 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 are using for debugging. In some cases, power transitions can interfere with debugging over USB 3.0.