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

[Bob Paddock]

On Thu, 7 Oct 2004 20:53:13 -0400, Brian Dean <address@hidden> wrote:

> > My work-around is to call the eeprom file eeprom.eep rather than
> > $(TARGET).eep.
>
> Ah, this is a clue.  Are you running this from a Makefile?  Can you
> provide the Makefile that you are using?  I wonder if another rule is
> overwriting te file somewhere, i.e., I suspect this might be a bug in
> your Makefile, as opposed to a bug in avrdude.

Makefile is created by MFILE.

You are correct it is not a AVRDUDE problem at all.  I never
checked the build process between doing a make and doing a
program step.  :-(

The file is actually corrupted before avrdude even starts.

This is what is doing it:

%.eep: %.elf
        @echo
        @echo $(MSG_EEPROM) $@
        -$(OBJCOPY) -j .eeprom --set-section-flags=.eeprom="alloc,load" \
        --change-section-lma .eeprom=0 -O $(FORMAT) $< $@

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.

Sorry for taking up your time.