I posted this in the WinDbg listserver it never got published.
On the target Usbview.exe says there are 24 USB ports available. Port 1-16 are “Not capable of Debug” and 17 onward all are “Debug Capable”.
I have 4 physical ports and they are mapped to port 1 - 4 as seen by UsbView.exe. None of them are “Capable of Debug”. Is it possible to remap one of the physical port to point to a port which is debug capable?
Related question. On the host when I run WinDbg using USB it should load a USB Debug Connection Driver. Unfortunately it complains the driver is not signed!! Why would MSFT ship a unsigned driver? Or what am I doing wrong?
BTW I am following the document:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-a-usb-3-0-debug-cable-connection
In Step 5 of this document they tell how to locate the physical port.
I did try a different target there also ran into the same issue. Debug Capable ports are not mapped to physical ports!!
On Sep 2, 2017, at 5:02 PM, xxxxx@gmail.com xxxxx@lists.osr.com wrote:
I posted this in the WinDbg listserver it never got published.
On the target Usbview.exe says there are 24 USB ports available. Port 1-16 are “Not capable of Debug” and 17 onward all are “Debug Capable”.
I have 4 physical ports and they are mapped to port 1 - 4 as seen by UsbView.exe. None of them are “Capable of Debug”. Is it possible to remap one of the physical port to point to a port which is debug capable?
No. You have to find the one port that is debug-capable. This is why USB debugging is so frustrating. There’s no standard for USB port numbering, and the onboard (and internal) USB ports are rarely labeled.
Related question. On the host when I run WinDbg using USB it should load a USB Debug Connection Driver. Unfortunately it complains the driver is not signed!! Why would MSFT ship a unsigned driver? Or what am I doing wrong?
Who complains? What version of windbg is this?
—
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thanks Tim, I always just do com port this time felt adventurous and tried USB, thanks for confirming my fear will just forget about USB and go for good old COM. All I need is a USB to COM converter cable.
I just installed the WinDbg as part of WDK install. The version is 10.0.15063.468.AMD64. In the host I set the debug port as USB and when I hit “OK” WinDbg tries to load the driver and that is when I get the error message saying. I think it is trying to load
C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\usb\usb2dbg.sys
Finally got it working. I want to close my query with a solution so others like me can benefit.
Ignore USBView part of the instructions
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-a-usb-3-0-debug-cable-connection
Use blue colored USB 3.0 or marked as SS ports without the battery(charging) symbol
Set your host to take unsigned drivers using bcdedit
Ensure BIOS option “Secure Boot” is disabled else bcdedit will not work
Remember disabling secure boot might cause other issues depending on your companies policy
On the Target also make sure you are using the correct USB 3.0 port and it is configured for a debug boot.
Then you are all set, it works like a charm.
This posting may be closed. Thanks to Tim Roberts for responding.