Re: [avr-gcc-list] mega48, mega88, mega168 support

[Theodore A. Roth]

On Wed, 14 Apr 2004, Galen Seitz wrote:

> Theodore A. Roth <address@hidden> wrote:
>
> > On Wed, 14 Apr 2004, Galen Seitz wrote:
> >
> > > Hi,
> > >
> > > I'm attempting to add support for the mega48, mega88, and possibly the
> > > mega168.  Is the mega168 an avr4 or avr5 architecture?  What are the
> > > differences between avr4 and avr5?
> >
> > This is done already:
> >
> >   http://savannah.nongnu.org/patch/?func=detailitem&item_id=2923
> >
> > Testing would be appreciated. ;-)
> >
>
> Guess I need to subscribe to the libc mailing list as well.  It's hard
> to keep track of all the pieces.  Can you help me with the mega48 status of
> all the tools?
>
> binutils      patch available on avr-libc site
> gcc           patch available on avr-libc site

I have tried to contact Marek and Denis to get their comments on these
patches, but got no response (it's only been a week or so). After I get
some user feed, I'll send the patches to the appropriate lists to try to
get them committed. (I don't have cvs-write access to binutils or gcc.)

> libc          patch available on avr-libc site / checked in to CVS ???

I'll commit that patch as soon as the header for the at90can128 is in
cvs.

> gdb           ???

Doesn't need any changes since it doesn't know anything about specific
devices anyways. Only needs either simulavr or avarice to be mega48
aware.

> simulavr      ???

Should not be too difficult to add the mega48/88/168 to get at least
what simulavr provides (which is limited). See the src/defn dir in the
latest cvs. Contact me off list and I'll help however I can.

> uisp          ???
> avrdude       ???

The parallel port SPI programmers should be easy as all the info is in
the datasheets (hopefully).

Stk500 support needs some more detective work. We need the device info
that AvrStudio sends down to the stk500. I think the only missing piece
is the special device code (which sadly is not the device code in the
datasheet).

> avarice       ???

Until I get my hands on the new jtagice mkII, I can't do much about it.
We probably need to ask Atmel for info.

My hope is that Atmel is using the same serial protocol as when
AvrStudio talks to the old jtagice.

Do these new devices have a jtag interface or are they strictly
debugWire?  I assume the latter.

<shameless plea>
If anyone wishes to donate a jtagice mkII and some test devices to me,
it might help speed things up.
</shameless plea>

>
> If help is needed to finish the mega48 stuff, please let me know where
> I can assist.

Help is always appreciated.

---
Ted Roth
PGP Key ID: 0x18F846E9
Jabber ID: address@hidden