1394 debugging - mostly working

WINDBG
1

I now have 1394 debugging working to some degree.

Here is my setup:

debuggee:
XP (no service pack - current drive not big enough to install sp1)

host:
XP sp1
windbg 6.1.0017.2

firewire using channel 42.
symbol path =
srv*d:\winddk\symbols\symsrv*http://msdl.microsoft.com/download/symbols;d:\winddk\symbols\mysyms

I can connect with windbg about 40% of the time. When it will not
connect, if I restart windbg, it will usually then connect.

I have not yet been able to have windbg running and sucessfully connect
the debugee when it is booting. Each time, the debugee boots as normal
and no message appears on the windbg screen. At that point I also can not
break into the debugger, and must restart windbg in order break in.

Clues?

Thanks,

Eric

2

Hi,
You need to disable the 1394 controler in the device manager on the target.

Yours
Roger

Roger Coote,
Senior Design Engineer
PowerVR Technologies, A Division of Imagination Technologies Ltd
Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ, UK
phone :+44 (1923) 260511 fax :+44 (1923) 268969
direct :+44 (1923) 277247
mailto:xxxxx@powervr.com www.powervr.com

-----Original Message-----
From: xxxxx@earthlink.net [mailto:xxxxx@earthlink.net]
Sent: 21 May 2003 15:18
To: Kernel Debugging Interest List
Subject: [windbg] 1394 debugging - mostly working

I now have 1394 debugging working to some degree.

Here is my setup:

debuggee:
XP (no service pack - current drive not big enough to install sp1)

host:
XP sp1
windbg 6.1.0017.2

firewire using channel 42.
symbol path =
srv*d:\winddk\symbols\symsrv*http://msdl.microsoft.com/download/symbols;d:\w
inddk\symbols\mysyms

I can connect with windbg about 40% of the time. When it will not
connect, if I restart windbg, it will usually then connect.

I have not yet been able to have windbg running and sucessfully connect
the debugee when it is booting. Each time, the debugee boots as normal
and no message appears on the windbg screen. At that point I also can not
break into the debugger, and must restart windbg in order break in.

Clues?

Thanks,

Eric

You are currently subscribed to windbg as: xxxxx@videologic.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3
  1. Get the latest debugger (6.2.7.4) from
    http://www.microsoft.com/whdc/ddk/debugging/default.mspx
  2. Disable the 1394 bus host controller (not the network adapter) on the
    target. If you want to disable the network adapter too, that is fine.
    Then reboot the target.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@earthlink.net
Sent: Wednesday, May 21, 2003 7:18 AM
To: Kernel Debugging Interest List
Subject: [windbg] 1394 debugging - mostly working

I now have 1394 debugging working to some degree.

Here is my setup:

debuggee:
XP (no service pack - current drive not big enough to install sp1)

host:
XP sp1
windbg 6.1.0017.2

firewire using channel 42.
symbol path =
srv*d:\winddk\symbols\symsrv*http://msdl.microsoft.com/download/symbols;
d:\winddk\symbols\mysyms

I can connect with windbg about 40% of the time. When it will not
connect, if I restart windbg, it will usually then connect.

I have not yet been able to have windbg running and sucessfully connect
the debugee when it is booting. Each time, the debugee boots as normal
and no message appears on the windbg screen. At that point I also can
not break into the debugger, and must restart windbg in order break in.

Clues?

Thanks,

Eric

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com