18f26k22 preload EEPROM

[technomation]

hi can't find the answer to this anywhere and hope someone can help I want to preload the eeprom of my device with data on loading, I have done this previously on 16f1936 using

[PCM programmer]

This is the easy way to do it in CCS. Let the compiler lookup the
eeprom address for you from its database:

[technomation]

hi thanks for the response,
just tried that and it works but only upto
#ROM getenv("EEPROM_ADDRESS") +0x70

after you go above this you get a verification error on loading to the pic

you can still access memory above 0x70 but not without deleting part of the previous #rom segment so seems like somekind of timout

any ideas ?

software is v5.016
thanks in advance (as it's 0240am here)

[PCM programmer]

A verification error comes from a programmer. What programmer are
you using ?

[PCM programmer]

I compiled the program shown below in MPLAB and then used the View
menu to look at eeprom values set by the compiler. It's setting eeprom
starting at address 0x80 to 0x55, 0xAA. Note that I have added the 'int8'
qualifier to the #rom statement, so the compiler fills eeprom with byte
data, instead with 16-bit words. Try this program and see what happens:

[gpsmikey]

Another option if you have room in Program memory - let the cpu initialize the eeprom the first time. Typically, it is a good idea to have a check-byte to allow you to verify the data in eeprom. On first start-up, that check byte is either 0 or FF (I forget). If it is in that state, then call a routine to set the initial values in eeprom and then set the checkbyte to the checksum or whatever you want to use. First run initializes the eeprom, from then on, all is normal (although you could use the init routine again if you wanted if something happened to corrupt the eeprom or you wanted to set everything back to the initial state).

mikey
_________________
mikey
-- you can't have too many gadgets or too much disk space !
old engineering saying: 1+1 = 3 for sufficiently large values of 1 or small values of 3

[technomation]

thanks for all your help guys

the programmer is a icd-u64

PCM you pointed out something I had never realised before #rom takes 16bit data! (which is actually the fix)

you know when the light bulb comes on..."I've just done things that way because I always have I works and I've never thought about it since" this is one of those moments...

all my data I store in the eeprom is actually 16 bit data.... I've been splitting it down into 8 bit chunks and inserting them one by one into a huge #rom segment (190 of them) , I've done this on pic projects (all 16f's until now) for as long as I've used the on chip eeproms which is years ...

just goes to show you learn newer better ways to do things everyday and why forums and there members are so important!

I've just converted the file into 16bit rom values... I now don't fear having to look at the eeprom file! (as it now contains real 16 bit data!)

but most importantly the verification error has gone away!

thanks once again