Re: [avr-gcc-list] AVRDUDE 4.3.0 Released

[Brian Dean]

On Wed, Jan 28, 2004 at 10:15:01AM -0700, Peter Hess wrote:

> I looked into doing that for the Atmega 162.  By just looking at the
> datasheet and comparing the avrdude.conf it wasn't really obvious
> how to do it.  It probably isn't trivial or all of the parts would
> have one - right?

Most folks just add the parts that they actually have in hand to the
config file.  I'd personally be reluctant to add definitions for which
I cannot test.

> Does someone have some instructions on how to do this?  I'd love to
> contribute what I create.

The instruction format looks intimidating, but I tried to make it look
very close to the instruction format that Atmel uses in their
datasheets.  However, the encoding is pretty straightforward - the
only thing that requires a little thought are the encoding of the 'a'
(address) bits, especially for parts with paged memory.  But it's not
too bad.  In fact, you can usually cut and paste the instruction
encoding from a similar part, similar being of the same memory layout.
Most other parameters have directly corresponding entries in the data
sheets which are usually found in the section entitled "Memory
Programming".

-Brian
-- 
Brian Dean, address@hidden
BDMICRO - Maker of the MAVRIC ATmega128 Dev Board
http://www.bdmicro.com/