linux-mips
[Top] [All Lists]

Re: Kernel Debugging on the DBAu1500

To: baitisj@evolution.com
Subject: Re: Kernel Debugging on the DBAu1500
From: Juan Quintela <quintela@mandrakesoft.com>
Date: Fri, 07 Mar 2003 13:02:52 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <20030306185345.W20129@luca.pas.lab> (Jeff Baitis's message of "Thu, 6 Mar 2003 18:53:45 -0800")
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030306185345.W20129@luca.pas.lab>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2.93
>>>>> "jeff" == Jeff Baitis <baitisj@evolution.com> writes:

Hi
        perhaps don't help, but try using 57600 bauds.  Some
        chipsets don't like 115200 bauds.

I have never used gdb on MIPS, but at least on intel, you need run a
program in your MIPS board (in intel it is gdbstart called).

Later, Juan.

jeff> Hi all:
jeff> I've been trying to get a kernel debugger running on my AMD DBAu1500.  It 
boots
jeff> up over a serial console. I enable "Remote GDB kernel debugging," and 
"Console
jeff> output to GDB."

jeff> Here's what I tell YAMON to do:

jeff> go . gdb gdbttyS=0 gdbbaud=115200

jeff> And on my x86 machine, I:

jeff> stty ispeed 115200 ospeed 115200 < /dev/ttyS1

jeff> /opt/hardhat/devkit/mips/fp_le/bin/mips_fp_le-gdb vmlinux
jeff> (gdb) target remote /dev/ttyS1 

jeff> GDB seems not to communicate. Here's what it says:

jeff> Ignoring packet error, continuing...
jeff> Ignoring packet error, continuing...
jeff> Ignoring packet error, continuing...
jeff> Couldn't establish connection to remote target
jeff> Malformed response to offset query, timeout

jeff> Suggestions?

jeff> Thanks in advance!




-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

<Prev in Thread] Current Thread [Next in Thread>