Re: [avrdude-dev] chip_erase and cycle_count cleanup

[Brian Dean]

On Sun, Nov 30, 2003 at 08:35:52PM +0100, Jan-Hinnerk Reichert wrote:

> > > BTW: Perhaps it would also be good to implement erase as an
> > > "update".
> >
> > I'm not sure what you mean by this.
> 
> I mean enqueue the erase operation in "updates" and have it done in 
> do_op(). And perhaps make it selectable by "-U", later.

Ah, ok.  I'm not sure this is really necessary, though.  It would make
parsing the -U option more difficult and the parameters don't really
fit the -U option.  For example, an erase unconditionally erases the
FLASH and sometimes the EEPROM on some parts depending on current fuse
bit settings.  Thus, supply the <memory> field of the -U parameter
does not apply and would be confusing.  Also, the <filename>:<type>
fields do not apply either.

> This way you can do things like Read EEPROM, Erase, Write Flash, 
> Rewrite EEPROM in one call.

You can do this now.  Remember, unless specified otherwise, an erase
is performed before writing FLASH memory:

        avrdude -p <part> -U eeprom:r:ee_save.hex:i -U flash:w:test.hex -U 
eeprom:w:ee.hex

-Brian