Hello, dear colleagues.
I want to debug a kernel driver using WinDbg.
The documentation says I need a USB 3.0 Super-Speed A/A debugging cable,
but in our stores we only found a USB 3.0 Super-Speed A/A cable or a
USB 3.0 Super-Speed A/A cable crossover.
Are they the same thing? If not, can someone show me the connection(pinout) diagram for a USB 3.0 Super-Speed A/A debugging cable so we can do this? Thank you.
crossover is not the same.
I do not know the pin order but I ordered this one: USB 3.0 Super-Speed A/A Debugging Cable -- DataPro
Yes, Thank You. Mr. Armattil.
Unless you need to debug your nic, using the network debugging interface is much easier.
1 Like
Section 5.38 (Chapter 5.5.2) of the USB 3.0 specification provides a wiring diagram for a USB 3.0 Standard-A to USB 3.0 Standard-A cable, designed for debugging operating systems and other host-to-host applications.
Question: Can this be used as a USB 3.0 Super-Speed debug cable to debug a target computer running the driver?
Yes, that's exactly what @apmattil proposed up above. It's still more trouble than network debugging.
I've had to deal with a handful of systems where the NIC wasn't supported by KDNET. I only had to resort to USB 3 once and it was fiddly, though less so than USB 2.0 
...Thankfully these weird systems these days tend to support KDNET via EEM and that makes life much, much easier.
-scott
Thanks everyone for the answers, but I don't understand what the network debugging interface is.
I want to debug an NDIS filter driver step by step. Remote debugging can be accomplished by connecting two computers with a network cable or a USB cable. Using a network cable for debugging, in my opinion, is unacceptable, since I'm debugging a network driver, so my only option is a USB cable. The USB cable that Microsoft suggested is a USB 3.0 Super-Speed A/A debug cable, I can't find in our stores. As for the USB 2.0 cable that Scott mentioned, I haven't read anything about it. Perhaps it would be more convenient.
USB 2.0 debugging only works with specific ports and only on certain hardware. For network debugging, all you need is a second NIC. Is that available on your machine?
1 Like
Yes, I can add a new network card to my computer. Thank you, Mr. Tim. Do you suggest replacing the USB debugging cable with a second network card? That would make my job easier.
Well, in MY experience, LAN debugging is the easiest and most consistent. I think some others have had luck with USB 3, but honestly, since I had something that worked, I never tried it. 
1 Like
When a NIC is enabled for KDNET debugging, the kernel takes ownership of it and Windows itself no longer sees that NIC device its original form. The kernel actually substitutes a virtual NIC of type "Microsoft Kernel Debug Network Adapter" which will be visible in the "Network Connections (ncpa.cpl) control panel applet and which can be used from within Windows, if desired.
In your case, you should see the virtual NIC for kernel debugging along with the other NIC for which you want to perform debugging of its device driver.