Re: [avrdude-dev] Why is eeprom file overwritten?

[Bob Paddock]

On Fri, 8 Oct 2004 17:10:45 +0200, Joerg Wunsch  
<address@hidden> wrote:

> As Bob Paddock wrote:
>
> > My .eep file was one I created externally, not part of the .elf
> > dependency, so it is getting over written.
>
> > Looks like I should move my EEPROM data into the .elf file.
>
> That's the common way many people do want: you create __attribute__
> ((section(".eeprom"))) variables in your C source, and have them
> automatically go into the .eep file.

It makes since that way, I just managed to shoot myself in the foot
because I already had the eeprom file I needed.


> I guess it would be worth the while to not burn the EEPROM file
> automatically anymore, but leave this decision to the user (e.g.  as a
> selectable option in Mfile).

I don't think that would have addressed my problem.  I still
wanted the eeprom file to be burned, I did not want to have
it created (over written).

> an EESAVE fuse bit anyway, it's probably no longer useful to have this
> written into the device by default.

I've had projects both ways, sometimes I want to burn the file every time,
other times only on the first burn.