avr-gcc-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] avr-as and debugging symbols


From: Theodore A. Roth
Subject: Re: [avr-gcc-list] avr-as and debugging symbols
Date: Mon, 30 Jun 2003 09:57:15 -0700 (PDT)


On Mon, 30 Jun 2003, Mark P Anderson wrote:


> When I got the tar of avr-gcc I don't believe that avr-gdb was
> part of it, at least it's not on my machine now.  So I'll have
> to go find and install it.  I don't mind using the command line
> version of gdb.

gdb is a separate project from gcc. Just grab the tarball and
configure with the --target=avr option.

> This is the subject that interests me the most.  What I need
> is a simulator/symbolic debugger that will have capabilities
> equivalent to AVR Studio but really work.  It have to run
> under Linux w/o X on modest h/w, laptop, 100Mhz, 40MB RAM,
> ..., also no Microsoft OS.
>
> I know of simulavr but when I last looked at it it was rather
> primitive.  I use gdb for other things and it would be fine,
> it's just that I didn't know how to interface it with an AVR
> simulator.  So what you're telling me is that simulavr is the
> place to start, it has some capability already, can interface
> to gdb, and may possibly be under development.

You could just yank the gdbserver.c from simulavr to do that. The
gdbserver.c in cvs has had all the simulavr specific code removed to
make it useable in other projects.

>
> My other ambition was to provide an ncurses gui so I could
> have at least two windows up, one source code and the other
> memory/register/io information displays.  That's why I was
> considering writing my own simulator.  Actually writing the
> instruction set simulator isn't all that difficult, its the
> user interface that's a lot of work.

This is already done for simulavr using a coprocess called
simulavr-disp. Simulavr does not display the source code since that is
better handled by emacs or gdb or some gui frontend for gdb.

>
> I'll check into simulavr and see how far along it is and how
> it interfaces to gdb.

It interfaces to gdb via gdb's remote serial protocol.

>
> At the present time I don't need JTAG ICE although I do have
> an ICE-200 that I don't use.  Has anyone ever used this product
> for anything?

I have one too, but have never used it. One of these days I'd like get
gdb to talk to it..

Ted Roth


reply via email to

[Prev in Thread] Current Thread [Next in Thread]