Hi Joe,
This is what I have been doing and only adds the CTRL-ALT-K.
Any other suggestions to get a stubborn 1394 connection working.
Ed
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Friday, March 11, 2011 5:00 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 debug connection problems.
Look in device manager on the target machine. If the 1394 controller is
banged out (yellow exclamation point) and the error code is code 31, then
that means that kd1394.dll found and took ownership of the 1394 hardware in
the target. Which is a good thing if you want debugging to actually work.
Joe.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Edward Dekker
Sent: Friday, March 11, 2011 1:57 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 debug connection problems.
Hi Joe,
How do I " make sure that after you boot the target machine 1394 controller
is banged out code 31" ?
Ed
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Friday, March 11, 2011 4:27 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 debug connection problems.
Make sure there is just 1 1394 controller in both the host debugger machine,
AND in the target machine.
Then make sure that after you boot the target machine 1394 controller is
banged out code 31 - it should be after debugging is enabled.
Fire up the debugger on the host (always use native bitness so that the
driver can install) hit ctrl alt k twice in windbg, and then boot the
target machine.
It should connect and break into the debugger.
Hit g.
Joe.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Edward Dekker
Sent: Friday, March 11, 2011 11:04 AM
To: Kernel Debugging Interest List
Subject: [windbg] 1394 debug connection problems.
Hi everyone,
I have a problem connecting WinDbg with a 1394 connection to a customer
supplied system. (The system does not have a serial port.)
I ran tests with both 32 bit Windows 7 and with Windows XP running on the
target system. I run 64 bit Vista on the host system.
I tried with host and target set to channel 0 and again with channel 10.
I tried the on motherboard 1394 controller (VIA).
When I stared the 32 bit WinDbg would not run and could not load the driver.
The error message told me to run the 64 bit WinDbg to load the driver. I
ran 64 bit WinDbg and saw the driver load. I assume this means I am not
using an old driver version.
With debugging enabled (via boot.ini or BCDEdit) Device Manager shows that
the 1394 was grabbed for debugging. (The yellow dot and exclamation point is
shown on the device because the standard driver could not load. When
debugging is disabled the standard driver loads without error.)
WinDbg running on the host (after CTL-ALT-D turns on trace) I get some trace
output. The trace shows:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Checking 1394 debug driver version.
Opened \.\DBG1394_INSTANCE00 <file:>
Timer Resolution set to 1000 usec.
Waiting to reconnect…
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
SYNCTARGET: Timeout.
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
SYNCTARGET: Timeout.
Pressing the WinDbg Break button we see:
…Synchronize: 80070002
SYNCTARGET: Timeout.
Synchronize:
…Synchronize: 80070002
Send sync break
Send Break in …
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!
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
…Synchronize: 80070002
Synchronize:
I plugged in a 1394 card from OSR (TI chip) and repeated the experiment.
After disabling the on-motherboard 1394 I get the same results.
I ran experiments on both targets with both the 32 and 64 bit versions of
WinDbg with the same results.
Any suggestions for the next step I can try to get debugging working?
Is there any trace mechanism for the 1394 connection process on the target
side?
Ed
—
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
—
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
—
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
—
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</file:>