RE: Problem attaching WinDbg to target after WDK7600 upgrade

You can download and install the latest Debugging Tools for Windows here:
http://www.microsoft.com/whdc/DevToo...g/default.mspx

And some tips for 1394 kernel debugging here
http://download.microsoft.com/downlo...WINHEC2004.ppt

Then follow the steps in the tool's documentation (Debugging Tools for
Windows->Debuggers->Installation and Setup->Kernel-Mode Setup

Depending on the Windows version, you may need to disable the 1394 host
controller of the target computer or the 1394 network adapter on the host
computer.

"scorbin" wrote:

> I installed the new WDK and get the following output when I run WinDbg
> now.
>
> ##########################################
> Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Checking 1394 debug driver version.
> Opened \\.\DBG1394_CHANNEL03
> Timer Resolution set to 976 usec.
> Waiting to reconnect...
> Wrote 0 of 1 bytes of the breakin packet.
> Failed to write breakin packet to target. Win32 error 0n2
> WARNING: The HOST cannot communicate with the TARGET!
> ##########################################
>
> I following the instructions in the relnotes.txt document and
> uninstalled the debugger device, 1394 host controller, all the old
> 1394dbg sys files and any infs that referenced them. I un/reinstalled
> WinDbg. I un/reinstalled the WDK. I installed the WDK w/o WinDbg,
> then manually installed it from CD and download. Nothing seems to be
> alleviating my problem.
>
> Does anybody have any other suggestions? I'm freakin stuck here and
> can't debug my device drivers and it's costing me big time. Any help
> would be greatly appreciated.
>
> Thanks!
> -Shane
>

FWIW, I am experiencing the exact same symptoms with what seems to be the
same context (was working, update to new WDK, firewire cannot connect remote
debugger).

"scorbin" wrote:

> I was using an older version of the debugger that used the
> 1394dbg2.sys driver and everything was working fine until I installed
> the new WDK. I've tried uninstalling and reinstalling each older
> version of the debugger all the way back to 6.6.3.5 with no success.
> My target host controller is banged out with a code 31 as was the case
> when things were working properly. I'm not sure what to try next.
>
> Do you have any other suggestions?
>
>
>
> On Sep 6, 5:20 pm, Jonathan Chang - MSFT
> <JonathanChangM...@discussions.microsoft.com> wrote:
> > You can download and install the latest Debugging Tools for Windows here:http://www.microsoft.com/whdc/DevToo...g/default.mspx
> >
> > And some tips for 1394 kernel debugging here:http://download.microsoft.com/downlo...b64-41f2-893d-...
> >
> > Then follow the steps in the tool's documentation (Debugging Tools for
> > Windows->Debuggers->Installation and Setup->Kernel-Mode Setup
> >
> > Depending on the Windows version, you may need to disable the 1394 host
> > controller of the target computer or the 1394 network adapter on the host
> > computer.
> >
> >
> >
> > "scorbin" wrote:
> > > I installed the new WDK and get the following output when I run WinDbg
> > > now.
> >
> > > ##########################################
> > > Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
> > > Copyright (c) Microsoft Corporation. All rights reserved.
> >
> > > Using 1394 for debugging
> > > Checking 1394 debug driver version.
> > > Opened \\.\DBG1394_CHANNEL03
> > > Timer Resolution set to 976 usec.
> > > Waiting to reconnect...
> > > Wrote 0 of 1 bytes of the breakin packet.
> > > Failed to write breakin packet to target. Win32 error 0n2
> > > WARNING: The HOST cannot communicate with the TARGET!
> > > ##########################################
> >
> > > I following the instructions in the relnotes.txt document and
> > > uninstalled the debugger device, 1394 host controller, all the old
> > > 1394dbg sys files and any infs that referenced them. I un/reinstalled
> > > WinDbg. I un/reinstalled the WDK. I installed the WDK w/o WinDbg,
> > > then manually installed it from CD and download. Nothing seems to be
> > > alleviating my problem.
> >
> > > Does anybody have any other suggestions? I'm freakin stuck here and
> > > can't debug my device drivers and it's costing me big time. Any help
> > > would be greatly appreciated.
> >
> > > Thanks!
> > > -Shane
>
>