I have an issue and it feels like I'm going at it the wrong way, would
appreciate suggestions.

I have a product that has a couple kB of default configuration data. We
currently add a data table as a header file during compile. (bunch of
#defined structures) Later the end user may need to make adjustments to
some few of these to suit their individual needs. There's a tool today that
pulls the entire data table into ram, allows the user to edit one or more
values from the front panel and then saves the table into flash with the
emulated EEPROM library and flip a bit to prevent using the defaults at
next power up. Net result - two copies of the data in FLASH.

Conceptually, two solutions come to mind. Have the emulated EEPROM tool put
it back into the same address space that the default copy came from. Or,
Have the compiler/linker/assembler load the default values in the same
space the emulated EEPROM uses. Functionally a similar outcome, but one is
a compile time solution, the other requires rewriting the emulation
functions. I suppose I need to leave room for some unknown third option
here too.

At the moment, I'm pretty sure I'm asking google the question wrong, as I'm
not finding useful results and I refuse to believe I'm truly pioneering in
this field. :-)


Thanks
-Denny
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.