Tony, you can probably write initialization data in assembly that clears
the EEPROM. When it matters for me, then I put a checksum in the EEPROM.
The runtime code checks this and initializes the EEPROM if it is not OK.
So I just set a garbage checksum in the assembly code and the chip takes
it from there. Obviously I do not expect new chips to have garbage in the
EEPROM, nor do I check for it (but I set the bad checksum as above).

Peter

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu