Hi,

I'm new to this list. Excuse me if my questions sound too trivial.

I'm getting the following error messages.

----------------------------------------------------------
Test Machine(MIPS) -->
RedBoot> fis load -d vmlinux
Image loaded from 0x80060000-0x80291085
RedBoot> exec -c "kgdb8250=0,115200 root=31:02 rootfstype=jffs2
init=/sbin/init"
Now booting linux kernel:
 Base address 0x80050000 Entry 0x80256000
 Cmdline : kgdb8250=0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init

Development Machine(x86) -->
# gdb ./vmlinux
GNU gdb Red Hat Linux (6.1post-1.20040607.43.0.1rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols
found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) set remotebaud 115200
(gdb)
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
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
(gdb)

----------------------------------------------------------
Development machine: x86
Test machine:  MIPS

Connected through a Serial(mips) to USB(x86) connector.

Test machine runs "mips-linux-2.6.15" cross-compiled on my development
machine.
I couldn't find KGDB patch for mips-linux-2.6.15 :( so I used
linux-2.6.15.5-kgdb-2.4.tar.bz2 KGDB patch for test machine.

----------------------------------------------------------
Questions:

1. Is my setup correct? Do i have to use development and test machines of
same architecture? MIPS platform is still supported or not?

2. I'm using a Serial to USB converter, is it fine or I have to use a null
modem cable only?

3. I believe I'm not using a right KGDB patch, is it so?

----------------------------------------------------------
.config files I tried -->

1.
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
.......
CONFIG_DEBUG_INFO=y
CONFIG_WANT_EXTRA_DEBUG_INFORMATION=y
CONFIG_KGDB=y
CONFIG_KGDB_CONSOLE=y
CONFIG_KGDB_8250_NOMODULE=y
CONFIG_CROSSCOMPILE=y
CONFIG_CMDLINE=""

----------------------------------------------------------
2.
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
.......
CONFIG_DEBUG_INFO=y
CONFIG_WANT_EXTRA_DEBUG_INFORMATION=y
CONFIG_KGDB=y
CONFIG_KGDB_CONSOLE=y
CONFIG_KGDB_ONLY_MODULES=y
CONFIG_CROSSCOMPILE=y
CONFIG_CMDLINE=""

----------------------------------------------------------
Command line options I used during kernel booting at test machine:

1. Cmdline : kgdb8250=0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init

2. Cmdline : kgdb8250=0,115200 kgdbwait root=31:02 rootfstype=jffs2
init=/sbin/init

3. Cmdline : console=ttyS0,115200 root=31:02 rootfstype=jffs2
init=/sbin/init

4. Cmdline : console=ttyS0,115200 kgdbwait root=31:02 rootfstype=jffs2
init=/sbin/init

None of the above solved my problem.

----------------------------------------------------------
I also tried using different BAUDRATES but no success there too.

Any help or pointers on this would be great.


Thanks
Amit Pundir
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to