Windows 8 USB debugging problem, ARM machine

Hi guys,

I am using a 8318 Win8 tools which has WinDbg 6.2.8318.0 x64 inside.
When the host tries to connect to the target via USB, the debugger installs an additional USB driver which is supposed to allow this connection. However, after the installation finishes I see a yellow bang in the device manager on “Microsoft USB device target” device… In the properties I see “Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”. This is strange, considering this is an MS tool & an MS driver…

The problem is, however, that my WinDbg cannot break into the target. The target is configured correctly (I suppose) with USB debugging enabled.

Any help would be appreciated.

Is the host x64? Can you use a x86 instead? If not: add the certificate with
which these drivers are signed to trusted roots? [only if your IT won’t
mind].

  • P.

wrote in message news:xxxxx@windbg…
> Hi guys,
>
> I am using a 8318 Win8 tools which has WinDbg 6.2.8318.0 x64 inside.
> When the host tries to connect to the target via USB, the debugger
> installs an additional USB driver which is supposed to allow this
> connection. However, after the installation finishes I see a yellow bang
> in the device manager on “Microsoft USB device target” device… In the
> properties I see “Windows cannot verify the digital signature for the
> drivers required for this device. A recent hardware or software change
> might have installed a file that is signed incorrectly or damaged, or that
> might be malicious software from an unknown source. (Code 52)”. This is
> strange, considering this is an MS tool & an MS driver…
>
> The problem is, however, that my WinDbg cannot break into the target. The
> target is configured correctly (I suppose) with USB debugging enabled.
>
> Any help would be appreciated.
>

Thanks. I’ve already tried that. x32 yields the same exact results - the USB target device has a yellow bang…

I believe this is expected, the kernel debug interface takes over the
device you are using for debugging, thus the actual driver for the device
cannot bind to it, fails to load and indicates this in device manager.
On Jun 8, 2012 5:00 PM, wrote:

> Thanks. I’ve already tried that. x32 yields the same exact results - the
> USB target device has a yellow bang…
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Arm debugging, and arm development in general, is not suitable for public forums. Please contact your Microsoft hw engagement pm for support

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, June 08, 2012 3:43 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windows 8 USB debugging problem, ARM machine

Hi guys,

I am using a 8318 Win8 tools which has WinDbg 6.2.8318.0 x64 inside.
When the host tries to connect to the target via USB, the debugger installs an additional USB driver which is supposed to allow this connection. However, after the installation finishes I see a yellow bang in the device manager on “Microsoft USB device target” device… In the properties I see “Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”. This is strange, considering this is an MS tool & an MS driver…

The problem is, however, that my WinDbg cannot break into the target. The target is configured correctly (I suppose) with USB debugging enabled.

Any help would be appreciated.


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer