Going back to basics, some advice on memory storage

[richard]

sorry about the sarcasm ,but doing it your way that's a lot of typing

still

DATA 8,CH1_Max.lowbyte
DATA 9,CH1_MAX.highbyte
DATA 10,CH2_Max.lowbyte

won't work data can only store constants

data @8, 123,34,23,15 ........................ for the other 92 values

and it can be readback with read

[HenrikOlsson]

DATA is used to store the value(s) in the EEPROM when the device is programmed. Ie. to get a "default" value in there. It's embedded in the .hex file image which get programmed into the device.
WRITE is used to store values in EEPROM during runtime.
It doesn't matter HOW the values got there, READ will access them.

You don't really have to keep track of the adresses etc, you can do
Ch1_On_Time DATA WORD 1234
Ch1_Of_Time DATA WORD 2345

This way you have created a label for each entry in the EEPROM which you can then use when your READ or WRITE from/to it in your code. Please note that Ch1_On_Time in this case is NOT your variable - it's ONLY a label. To actually USE it in your program you need to READ it from EEPROM and Place it an ordinary variable - but you're already doing that.

Using arrays, the EXT modifer, and indexing thru the data as in Richards example is probably more efficient code wise but may not be the easiest way to debug and/or understand. YMMV.

/Henrik.

[Scampy]

Henrik,

Thank you for your very informative post. I agree that Richards guidance in using the array and modifier makes for tighter compact code. I just thought that in this case it might of muddied the water a little when I was trying to explain my question.

[Scampy]

Henrik,

If I follow your post correctly I can do the following

DATA @8,0 

EE_CH1_Max DATA WORD 4095
EE_CH2_Max DATA WORD 4095

etc

and then

read EE_CH1_Max, WORD CH1_Max
read EE_CH2_Max, WORD CH2_Max

The part I can't get my head round is assuming you place the data statement at the start of the code so this happens when the code is run, what distinguishes it from a fresh install and a reboot as surely the code is executed from the start when powered up and will use the data command when it reaches that line of code ?

[Scampy]

Oh it's so much easier with labels than using all that location, lowbyte hughtbyte stuff !!!

I now have a set of preset values loaded first time after the chip is programmed, and user variables saved once changed by the user, which are retained in the event of a power fail...

Now to do a few more bits before following Richards examples to tidy up the code and make ot a bit more compact...