Date: Wed, 09 Feb 2005 10:47:18 -0500 From: Stephan Uphoff <ups@tree.com> To: Gerald Heinig <gheinig@syskonnect.de> Cc: hackers@freebsd.org Subject: Re: Firewire blues Message-ID: <1107964038.6309.1137.camel@palm.tree.com> In-Reply-To: <4209C640.3070502@syskonnect.de> References: <420731DD.3050206@syskonnect.de> <42088232.1030001@syskonnect.de> <1107888844.6309.221.camel@palm.tree.com> <4209C640.3070502@syskonnect.de>
index | next in thread | previous in thread | raw e-mail
On Wed, 2005-02-09 at 03:13, Gerald Heinig wrote: > Stephan Uphoff wrote: > > There are two ways using kgdb to debug a target with firewire. > > The first way basically replaces the slow serial cable for communication > > to the remote target gdb stub. > > The second way uses the remote DMA capabilities of firewire to directly > > read memory of the target WITHOUT using any debugging software/stub on > > the target. (Think remote core file) > > > > Greg Lehey wrote a nice kernel debugging tutorial that explains both > > types of firewire debugging. > > http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf > > > > This should get you started with only minor adjustments (gdb->kgdb) . > > This is actually the paper I'm using. I've followed the instructions on > both methods, but I can't get it to work. The direct machine-machine > connection is fine (ie. the one with dconschat). It's the kgdb > connection that doesn't work. > I presume it worked out of the box for you then? Once I linked in dcons, dcons_crom and firewire into the kernel everything worked. (I think only dcons is really needed - maybe a link set issue?) I only used the gdb stub method. Can you send me your dmesg? (After you linked the dcons stuff into the kernel) Stephanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1107964038.6309.1137.camel>