Perform the same steps to determine whether the internal USB connector is suitable for kernel debugging. In that case, you can look for a physical USB connector inside the computer. It could be that there is no external physical USB connector that is associated with a debug port on an EHCI controller. If UsbView shows your device connected to the EHCI host controller and port that you identified as the debug port, then you have found a physical USB connector that you can use for debugging. Refresh UsbView to see where your device is located. To find the physical connector, plug any USB 2.0 device into any USB connector on the target computer. In the preceding example, the bus number is 0, the device number is 29, and the function number is 7.Īfter you have identified the EHCI controller and the port number that supports debugging, the next step is to locate the physical USB connector that is associated with the correct port number. Make a note of the bus, device, and function numbers for the EHCI controller that you intend to use for debugging. Note Many EHCI host controllers support debugging on port 1, but some EHCI host controllers support debugging on port 2. Xxx xxx xxx USB2 Enhanced Host Controller - 293A For example, UsbView displays this output for an EHCI host controller that supports debugging on port 1. Look for an indication that a host controller supports debugging, and look for the number of the debug port. In UsbView, expand the nodes of the EHCI host controllers. For example, you could look for controllers that are listed as Enhanced. In UsbView, locate all of the host controllers that are compatible with the EHCI specification. The UsbView tool is included in Debugging Tools for Windows. On the target computer, launch the UsbView tool. On the target computer, an EHCI (USB 2.0) host controller that supports debugging On the host computer, an EHCI (USB 2.0) host controller You can find these cables with an Internet search for the term USB 2.0 debug cable. This cable is not a standard USB 2.0 cable because it has an extra hardware component that makes it compatible with the USB2 Debug Device Functional Specification. 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 2.0 cable requires the following hardware:Ī USB 2.0 debug cable.
#USB DEBUGGING WINDOWS 10 BIOS HOW TO#
This topic describes how to set up USB 2.0 debugging manually. Debugging Tools for Windows supports kernel debugging over a USB 2.0 cable.
0 kommentar(er)
