Re: [avr-gcc-list] including default eeprom values in flash memory

[Michael Clift]

Thanks for all the responses guys, some interesting ideas.
I don't really want to put all of my EEPROM data into one structure, as 
I have many eeprom variables with initializers distributed across a 
number of files.

What I ended up doing, was to change the .eep output format to binary, 
then I copied this to an object file as described here 
http://www.nongnu.org/avr-libc/user-manual/FAQ.html#faq_binarydata
I then linked this object into my main code. It works a treat, only I 
have to build my code twice to get the initial values updated to flash, 
once to create .eep, and again to link in the object.

The main reason for doing this, is that I have a boot loader that I want 
our clients to be able to use, only the boot loader does not support 
eeprom loading. It also saves me having to program the eeprom in production.


Regards, Michael.