On Fri, 2003-03-07 at 05:23, Pete Popov wrote: > Jeff, > > Take a look at the board and remind me if the second serial port is > actually uart2, where the first is uart0. Sorry, I meant uart3, which would be a reason why the UART2_ADDR define below wouldn't work. Pete > I think it might be. If that's > the case, arch/mips/au1000/common/dbg_io.c has this define if kgdb is > defined: > > #define DEBUG_BASE UART2_ADDR > > That needs to get fixed. It would be better to parse the command line > for something like "kgdb=ttyS2,115200". > > Pete > > On Thu, 2003-03-06 at 18:53, Jeff Baitis wrote: > > Hi all: > > > > I've been trying to get a kernel debugger running on my AMD DBAu1500. It boots > > up over a serial console. I enable "Remote GDB kernel debugging," and "Console > > output to GDB." > > > > Here's what I tell YAMON to do: > > > > go . gdb gdbttyS=0 gdbbaud=115200 > > > > And on my x86 machine, I: > > > > stty ispeed 115200 ospeed 115200 < /dev/ttyS1 > > > > /opt/hardhat/devkit/mips/fp_le/bin/mips_fp_le-gdb vmlinux > > (gdb) target remote /dev/ttyS1 > > > > GDB seems not to communicate. Here's what it says: > > > > Ignoring packet error, continuing... > > Ignoring packet error, continuing... > > Ignoring packet error, continuing... > > Couldn't establish connection to remote target > > Malformed response to offset query, timeout > > > > Suggestions? > > > > Thanks in advance! > > > > -Jeff > > >
