gdb support for m32c?

gdb support for m32c?

[Hans-Wolfgang Loidl]

Hi,

The GCC readinglist claims that GDB includes a simulator
for the m32c processor.
However, downloading the latest gdb snapshot I only found
a dir m32r (the RISC rather than CISC version) in the
sim/ dir.

Can somebody enlighten me whether GDB does support the
m32c, and if so how to include support for it, so that I can
at least use it as simulator for GCC generated m32c-elf 
binaries.

Thanks!
--
 HW

Re: gdb support for m32c?

[Daniel Jacobowitz]

On Wed, Mar 08, 2006 at 11:11:33PM +0100, Hans-Wolfgang Loidl wrote:
> Hi,
> 
> The GCC readinglist claims that GDB includes a simulator
> for the m32c processor.
> However, downloading the latest gdb snapshot I only found
> a dir m32r (the RISC rather than CISC version) in the
> sim/ dir.
> 
> Can somebody enlighten me whether GDB does support the
> m32c, and if so how to include support for it, so that I can
> at least use it as simulator for GCC generated m32c-elf 
> binaries.

The latest CVS version of GDB does include the m32c simulator;
you may have been looking at an older release branch snapshot.
However, GDB doesn't yet have an m32c port; I think it got held up in
review at some point, but I don't remember.

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb support for m32c?

[Hans-Wolfgang Loidl]

Hi Daniel,

Thanks for the swift reply. 
I now checked out the HEAD of the gdb cvs rep with the m32c code in
sim. Does "not supported yet" mean that the simulator itself doesn't
work, or just that some GDB features don't work, yet?
As said, at the moment I'd only need the simulator, and I'd happy
with a version even if it's still a bit unstable.

If not, any comments how close that would be to completion? We just
started work on a project that still goes at least 2 years, so we could
plan things around a rough timeplan.

Cheers,
--
 HW

On Wed, 8 Mar 2006 22:24:49 -0500
Daniel Jacobowitz <drow@false.org> wrote:

> On Wed, Mar 08, 2006 at 11:11:33PM +0100, Hans-Wolfgang Loidl wrote:
> > Hi,
> > 
> > The GCC readinglist claims that GDB includes a simulator
> > for the m32c processor.
> > However, downloading the latest gdb snapshot I only found
> > a dir m32r (the RISC rather than CISC version) in the
> > sim/ dir.
> > 
> > Can somebody enlighten me whether GDB does support the
> > m32c, and if so how to include support for it, so that I can
> > at least use it as simulator for GCC generated m32c-elf 
> > binaries.
> 
> The latest CVS version of GDB does include the m32c simulator;
> you may have been looking at an older release branch snapshot.
> However, GDB doesn't yet have an m32c port; I think it got held up in
> review at some point, but I don't remember.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery

Re: gdb support for m32c?

[Daniel Jacobowitz]

On Thu, Mar 09, 2006 at 03:41:34PM +0100, Hans-Wolfgang Loidl wrote:
> Hi Daniel,
> 
> Thanks for the swift reply. 
> I now checked out the HEAD of the gdb cvs rep with the m32c code in
> sim. Does "not supported yet" mean that the simulator itself doesn't
> work, or just that some GDB features don't work, yet?
> As said, at the moment I'd only need the simulator, and I'd happy
> with a version even if it's still a bit unstable.

The simulator should be fine, as far as I know.

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb support for m32c?

[DJ Delorie]

> > I now checked out the HEAD of the gdb cvs rep with the m32c code in
> > sim. Does "not supported yet" mean that the simulator itself doesn't
> > work, or just that some GDB features don't work, yet?
> > As said, at the moment I'd only need the simulator, and I'd happy
> > with a version even if it's still a bit unstable.
> 
> The simulator should be fine, as far as I know.

Alas, it needs some patches, although they're minor.  I use the
simulator a LOT so it's fairly stable.

I missed that the m32c sim had been approved.  I'm supposed to be the
m32c sim maintainer but Jim didn't add me as part of the commit
process.  How to proceed?

Also, while I can get the simulator to build, it currently doesn't get
that far because it has a dependency on gdb being at least configured,
which doesn't happen yet.  That's why I didn't notice my builds
suddenly including the simulator :-P

Re: gdb support for m32c?

[Hans-Wolfgang Loidl]

Hi DJ,

In the meantime I managed to build the m32c simulator from the CVS HEAD,
and with that version I can now run simple C programs, and also some 
programs compiled via C from out high-level language
So, I'm a happy user (for now)!

I noticed, though, that the simulator can't handle argv input: it gives
a null pointer reference.

Any patches that you have, and other hints on using it tools etc would
be very welcome!

Cheers,
--
 HW

On Fri, 10 Mar 2006 16:30:19 -0500
DJ Delorie <dj@redhat.com> wrote:

> 
> > > I now checked out the HEAD of the gdb cvs rep with the m32c code
> > > in sim. Does "not supported yet" mean that the simulator itself
> > > doesn't work, or just that some GDB features don't work, yet?
> > > As said, at the moment I'd only need the simulator, and I'd happy
> > > with a version even if it's still a bit unstable.
> > 
> > The simulator should be fine, as far as I know.
> 
> Alas, it needs some patches, although they're minor.  I use the
> simulator a LOT so it's fairly stable.
> 
> I missed that the m32c sim had been approved.  I'm supposed to be the
> m32c sim maintainer but Jim didn't add me as part of the commit
> process.  How to proceed?
> 
> Also, while I can get the simulator to build, it currently doesn't get
> that far because it has a dependency on gdb being at least configured,
> which doesn't happen yet.  That's why I didn't notice my builds
> suddenly including the simulator :-P

Re: gdb support for m32c?

[DJ Delorie]

> In the meantime I managed to build the m32c simulator from the CVS
> HEAD, and with that version I can now run simple C programs, and
> also some programs compiled via C from out high-level language So,
> I'm a happy user (for now)!

Like I said, the patches are minimal.  Example: shift counts bigger
than 16 are not properly truncated, a few more simulated hardware
bits, etc.

> I noticed, though, that the simulator can't handle argv input: it gives
> a null pointer reference.

There's no argv support.  Boards don't have command lines ;-)

I have a pile of r8c, m16c, and m32c boards on my desk.  I try to make
the simulator compatible with them, so I can run the same images on
both.

If you're interested in adding argv support, it might be a good idea
to wait for the gdb integration, since gdb needs to know how to set
argv also.

Re: gdb support for m32c?

[Hans-Wolfgang Loidl]

Hi DJ,

On Fri, 10 Mar 2006 17:55:29 -0500
DJ Delorie <dj@redhat.com> wrote:

> 
> > In the meantime I managed to build the m32c simulator from the CVS
> > HEAD, and with that version I can now run simple C programs, and
> > also some programs compiled via C from out high-level language So,
> > I'm a happy user (for now)!
> 
> Like I said, the patches are minimal.  Example: shift counts bigger
> than 16 are not properly truncated, a few more simulated hardware
> bits, etc.
> 
> > I noticed, though, that the simulator can't handle argv input: it
> > gives a null pointer reference.
> 
> There's no argv support.  Boards don't have command lines ;-)
> 
> I have a pile of r8c, m16c, and m32c boards on my desk.  I try to make
> the simulator compatible with them, so I can run the same images on
> both.
> 
> If you're interested in adding argv support, it might be a good idea
> to wait for the gdb integration, since gdb needs to know how to set
> argv also.

It's no biggy; would just be handy for testing stuff. I'll be in touch
if I find more serious things. For now I mainly stick to the simulator,
but in the end we'll work on an m32c based board, to evaluate.

What do you use to flash the code onto the actual board?

Cheers,
-- 
 HW

Re: gdb support for m32c?

[DJ Delorie]

> What do you use to flash the code onto the actual board?

I wrote a program to talk to the KD30 debugger module pre-loaded in
the chips.  IIRC there's also a binary downloader (non-kd30) for the
m16c.  However, my program is kinda specific to the boards I have.

The flash specs are all available online, it's just a matter of
writing the code to do it.  A gdb remote stub shouldn't be *that*
tricky to write.

Re: gdb support for m32c?

[Daniel Jacobowitz]

On Fri, Mar 10, 2006 at 04:30:19PM -0500, DJ Delorie wrote:
> Alas, it needs some patches, although they're minor.  I use the
> simulator a LOT so it's fairly stable.
> 
> I missed that the m32c sim had been approved.  I'm supposed to be the
> m32c sim maintainer but Jim didn't add me as part of the commit
> process.  How to proceed?

I don't know.  I vaguely remember this coming up when the patch was
submitted; ah, there was some confusion about whether there was already
an m32c port and it was already yours.  If you want maintainership of
this sim, I don't think anyone will object; could you add yourself to
sim/MAINTAINERS?

> Also, while I can get the simulator to build, it currently doesn't get
> that far because it has a dependency on gdb being at least configured,
> which doesn't happen yet.  That's why I didn't notice my builds
> suddenly including the simulator :-P

It'd be nice to get the GDB port finalized, one way or another.

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb support for m32c?

[DJ Delorie]

> If you want maintainership of this sim, I don't think anyone will
> object; could you add yourself to sim/MAINTAINERS?

Done, attached.  Thanks!

> It'd be nice to get the GDB port finalized, one way or another.

It's still waiting for Jim's prologue analyzer work:
http://sources.redhat.com/ml/gdb-patches/2006-01/msg00341.html


2006-03-13  DJ Delorie  <dj@redhat.com>

	* MAINTAINERS: Add self as m32c sim maintainer.

Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/sim/MAINTAINERS,v
retrieving revision 1.16
diff -p -U3 -r1.16 MAINTAINERS
--- MAINTAINERS	26 May 2005 21:37:09 -0000	1.16
+++ MAINTAINERS	14 Mar 2006 02:35:53 -0000
@@ -15,6 +15,7 @@ igen		(igen simulators)
 ppc		Andrew Cagney <ac131313@redhat.com>
 m68hc11		Stephane Carrez <stcarrez@nerim.fr>
 sh		(global maintainers)
+m32c		DJ Delorie <dj@redhat.com>
 common		Ben Elliston <bje@gnu.org>
 common		Frank Ch. Eigler <fche@redhat.com>
 *		(target, then global maintainers)