[linuxsh-dev] GDB configuration?

[Bryan R. <br...@ix...>]

Hello linuxsh-dev,

The following is a copy of a post I made this morning to linux-sh.
However, I believe this list is probably more appropriate. Since writing
it I have messed with gdb some more but I really think I have it
misconfigured, since there is no code in sh-boot to respond to the
packets it's sending the board on startup. Anyway:

---

I have been lurking on this list for a couple days while experimenting
with as much of the LinuxSH project sources as possible, trying to get
Linux up on a custom (basically bare) SH4 board. I successfully built
all the cross development tools, and have the sh-ipl/sh-boot stub
running on the system, and talking to my x86 linux workstation over the
serial port (38400bps). I can go in with a terminal program and get the
warranty, the license, etc... but what I really want is to get the
kernel running. However, for some reason, the GDB on my workstation just
does not want to talk to the embedded board. I have experimented with as
many versions of the boot/stub as I could find, including the one on
sourceforge CVS (which has some rather broken code in places), as well
as both gdb-sh-stub-2000-07-09.tar.gz and  sh-ipl+g-2000-08-11.tar.gz
from ftp://ftp.m17n.org/pub/super-h/ Since I have tried so much on the
embedded side, I now believe the problem is now with the GDB on the
workstation (which is fortunate, because it's much easier to debug). The
documentation on http://linuxsh.sourceforge.net/ is great, but says
nothing about GDB... however, http://www.m17n.org/linux-sh/dist/HOWTO
mentions that a patch is needed against GDB to get it talking to an
embedded board. So, I guess what I need to know is, is that patch still
needed against the gdb on linuxsh sourceforge CVS, and if so, where can
I get it? I would greatly appreciate an updated walkthrough of how to
get GDB compiled and talking to sh-boot/sh+ipl, as well as advice on
what version of the stub I should be working with, since it looks like
there are three forks of the same code (CVS sh-boot, gdb-sh-stub, and
sh-ipl+g).

I am assuming it is possible to load a kernel into an arbitrary memory
location (over the serial port) once GDB and the SH4 stub are talking?

Thanks to everyone for the great progress that has been made on LinuxSH.
I look forward to working with you in the future.

Regards,

Bryan Rittmeyer
mailto:br...@ix...