I’m trying to setup the kernel debug over the USB 3.0 debug port between the tablet and laptop. The tablet device is the target machine and the laptop is the host machine. They both have one native USB 3.0 port and are running on Win8 64bit.
The first issue I saw the issue on the host machine is that the device manager always show the problematic device node “Unknown USB Device (Port Reset Failed)” after I plugin the USB 3.0 debug cable. I searched online and saw nothing about it. Does anyone here know the reason and the way to solve it? Do I need to install any driver for that? I paste its setup api log here for your reference. It looks that the VID of the cable is 0. Is it bad cable?
>> [Device Install (DiShowUpdateDevice) - USB\VID_0000&PID_0008\6&1A9CCABE&0&2]
>> Section start 2013/02/04 15:49:47.132
cmd: “C:\WINDOWS\system32\mmc.exe” C:\WINDOWS\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 15:49:47.132
dvi: No class installer for ‘Unknown USB Device (Link in Compliance Mode)’
dvi: No CoInstallers found
dvi: Default installer: Enter 15:49:47.132
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 15:49:47.147
ndv: {Update Driver Software Wizard for USB\VID_0000&PID_0008\6&1A9CCABE&0&2}
dvi: {DIF_SELECTDEVICE} 15:49:55.352
dvi: No class installer for ‘Unknown USB Device (Link in Compliance Mode)’
dvi: No CoInstallers found
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 15:49:55.367
sto: {Import Driver Package: C:\WINDOWS\INF\usb.inf} 15:50:00.666
sto: Driver Store = C:\WINDOWS\System32\DriverStore [Online] (6.2.9200)
sto: Driver Package = C:\WINDOWS\INF\usb.inf
sto: Architecture = amd64
sto: Flags = 0x00000000
inf: Provider = Microsoft
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Driver Version = 06/21/2006,6.2.9200.16384
inf: Version Flags = 0x00000001
sto: Driver package already imported as ‘usb.inf’.
sto: Driver Store Filename = C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64_7f2003710f5dfe2c\usb.inf
sto: {Import Driver Package: exit(0x00000000)} 15:50:00.698
dvi: Searching for hardware ID(s):
dvi: usb\port_link_compliance_mode
dvi: Searching for compatible ID(s):
dvi: usb\port_link_compliance_mode
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Plug and Play Service: Device Install for USB\VID_0000&PID_0008\6&1A9CCABE&0&2}
ndv: Infpath=C:\WINDOWS\INF\usb.inf
ndv: DriverNodeName=usb.inf:392c3d53becab253:BADDEVICE.Dev:6.2.9200.16384:usb\port_link_compliance_mode
ndv: DriverStorepath=C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64_7f2003710f5dfe2c\usb.inf
dvi: Searching for hardware ID(s):
dvi: usb\port_link_compliance_mode
dvi: Searching for compatible ID(s):
dvi: usb\port_link_compliance_mode
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
ndv: {Core Device Install} 15:50:00.823
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64_7f2003710f5dfe2c\usb.inf}
sto: Driver Store = C:\WINDOWS\System32\DriverStore [Online] (6.2.9200)
sto: Driver Package = usb.inf_amd64_7f2003710f5dfe2c
sto: Flags = 0x00020000
sto: Source Filter = usb\port_link_compliance_mode
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Class Status = Configurable Critical
inf: {Configure Driver: Unknown USB Device (Link in Compliance Mode)}
inf: Manufacturer = (Standard USB Host Controller)
inf: Section Name = BADDEVICE.Dev.NT
inf: Hardware Id = USB\PORT_LINK_COMPLIANCE_MODE
inf: {Configure Driver Configuration: BADDEVICE.Dev.NT}
inf: Service Name = inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} sto: {Configure Driver Package: exit(0x00000000)} dvi: Install Device: Configuring device (usb.inf:usb\port_link_compliance_mode,BADDEVICE.Dev.NT). 15:50:00.869 dvi: Install Device: Configuring device completed. 15:50:00.869 dvi: Install Device: Restarting device. 15:50:00.869 dvi: Install Device: Restarting device completed. 15:50:00.869 ndv: {Core Device Install - exit(0x00000000)} 15:50:00.885 ump: {Plug and Play Service: Device Install exit(00000000)} dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 15:50:00.885 dvi: No class installer for ‘Unknown USB Device (Link in Compliance Mode)’ dvi: No CoInstallers found dvi: Default installer: Enter 15:50:00.885 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 15:50:00.902 ndv: {Update Driver Software Wizard exit(00000000)} <<< Section end 2013/02/04 15:50:03.914 <<< [Exit status: SUCCESS]
USB 3.0 as a debug transport is supported as of Windows 8. I haven’t had a
chance to try it myself though (no XHCI controller on my dev box), so I
don’t have much experience to share.
OP: Have you gone through the steps outlined here?
Also, not all usb 3controllers have debug registers. Are you sure yours has them?
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Monday, February 4, 2013 1:56 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Failed in setting up kernel debug over the USB 3.0 debug cable
USB 3.0 as a debug transport is supported as of Windows 8. I haven’t had a chance to try it myself though (no XHCI controller on my dev box), so I don’t have much experience to share.
OP: Have you gone through the steps outlined here?
Not all xHCI host controllers support the debug capability. Have you
checked to make sure you are using one that does?
{Configure Driver: Unknown USB Device (Link in Compliance Mode)} -> your
device and host did not link up correctly. Or if this is the port you are
using to connect via the debug cable, it didn’t work. One side gave up and
went into a special compliance mode, only used for testing of the USB 3.0
link, not communication.
Regards,
Diane
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Monday, February 4, 2013 1:09 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Failed in setting up kernel debug over the USB 3.0 debug
cable
Hi All,
I’m trying to setup the kernel debug over the USB 3.0 debug port between the
tablet and laptop. The tablet device is the target machine and the laptop is
the host machine. They both have one native USB 3.0 port and are running on
Win8 64bit.
The first issue I saw the issue on the host machine is that the device
manager always show the problematic device node “Unknown USB Device (Port
Reset Failed)” after I plugin the USB 3.0 debug cable. I searched online and
saw nothing about it. Does anyone here know the reason and the way to solve
it? Do I need to install any driver for that? I paste its setup api log here
for your reference. It looks that the VID of the cable is 0. Is it bad
cable?
>> [Device Install (DiShowUpdateDevice) -
>> USB\VID_0000&PID_0008\6&1A9CCABE&0&2]
>> Section start 2013/02/04 15:49:47.132
cmd: “C:\WINDOWS\system32\mmc.exe” C:\WINDOWS\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 15:49:47.132
dvi: No class installer for ‘Unknown USB Device (Link in
Compliance Mode)’
dvi: No CoInstallers found
dvi: Default installer: Enter 15:49:47.132
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 15:49:47.147
ndv: {Update Driver Software Wizard for
USB\VID_0000&PID_0008\6&1A9CCABE&0&2}
dvi: {DIF_SELECTDEVICE} 15:49:55.352
dvi: No class installer for ‘Unknown USB Device (Link in
Compliance Mode)’
dvi: No CoInstallers found
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 15:49:55.367
sto: {Import Driver Package: C:\WINDOWS\INF\usb.inf} 15:50:00.666
sto: Driver Store = C:\WINDOWS\System32\DriverStore
[Online] (6.2.9200)
sto: Driver Package = C:\WINDOWS\INF\usb.inf
sto: Architecture = amd64
sto: Flags = 0x00000000
inf: Provider = Microsoft
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Driver Version = 06/21/2006,6.2.9200.16384
inf: Version Flags = 0x00000001
sto: Driver package already imported as ‘usb.inf’.
sto: Driver Store Filename =
C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64_7f2003710f5dfe2
c\usb.inf
sto: {Import Driver Package: exit(0x00000000)} 15:50:00.698
dvi: Searching for hardware ID(s):
dvi: usb\port_link_compliance_mode
dvi: Searching for compatible ID(s):
dvi: usb\port_link_compliance_mode
dvi: Class GUID of device changed to:
{36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Plug and Play Service: Device Install for
USB\VID_0000&PID_0008\6&1A9CCABE&0&2}
ndv: Infpath=C:\WINDOWS\INF\usb.inf
ndv:
DriverNodeName=usb.inf:392c3d53becab253:BADDEVICE.Dev:6.2.9200.16384:usb\por
t_link_compliance_mode
ndv:
DriverStorepath=C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64
_7f2003710f5dfe2c\usb.inf
dvi: Searching for hardware ID(s):
dvi: usb\port_link_compliance_mode
dvi: Searching for compatible ID(s):
dvi: usb\port_link_compliance_mode
dvi: Class GUID of device changed to:
{36fc9e60-c465-11cf-8056-444553540000}.
ndv: {Core Device Install} 15:50:00.823
sto: {Configure Driver Package:
C:\WINDOWS\System32\DriverStore\FileRepository\usb.inf_amd64_7f2003710f5dfe2
c\usb.inf}
sto: Driver Store =
C:\WINDOWS\System32\DriverStore [Online] (6.2.9200)
sto: Driver Package =
usb.inf_amd64_7f2003710f5dfe2c
sto: Flags = 0x00020000
sto: Source Filter = usb\port_link_compliance_mode
inf: Class GUID =
{36fc9e60-c465-11cf-8056-444553540000}
inf: Class Status = Configurable Critical
inf: {Configure Driver: Unknown USB Device (Link in
Compliance Mode)}
inf: Manufacturer = (Standard USB Host
Controller)
inf: Section Name = BADDEVICE.Dev.NT
inf: Hardware Id =
USB\PORT_LINK_COMPLIANCE_MODE
inf: {Configure Driver Configuration:
BADDEVICE.Dev.NT}
inf: Service Name = inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} sto: {Configure Driver Package: exit(0x00000000)} dvi: Install Device: Configuring device (usb.inf:usb\port_link_compliance_mode,BADDEVICE.Dev.NT). 15:50:00.869 dvi: Install Device: Configuring device completed. 15:50:00.869 dvi: Install Device: Restarting device. 15:50:00.869 dvi: Install Device: Restarting device completed. 15:50:00.869 ndv: {Core Device Install - exit(0x00000000)} 15:50:00.885 ump: {Plug and Play Service: Device Install exit(00000000)} dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 15:50:00.885 dvi: No class installer for ‘Unknown USB Device (Link in Compliance Mode)’ dvi: No CoInstallers found dvi: Default installer: Enter 15:50:00.885 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 15:50:00.902 ndv: {Update Driver Software Wizard exit(00000000)} <<< Section end 2013/02/04 15:50:03.914 <<< [Exit status: SUCCESS]
I also watched the video on the Channel 9 about how to setup the kernel debug over the USB 3.0 cable. It should be pretty easy without doing any extra things.
How can I ensure whether my xHCI usb 3 controllers have debug capabilities? I tried to use the usbview.exe but the problem is the device node is an invalid one with yellow mark.