> > there is no problem with reading EEPROM very often?
>
> Maybe that reading an EEPROM location takes more time
> then reading a normal RAM location ?

The only extra command that has to be issued is to set RD
(assuming that other relevant EECON1 bits have been written
beforehand)

Depending on the circumstances it might take longer to read
a RAM location. For example if you need to change banks. I
doubt that, except in the most critically time-dependent apps, it
would make much difference where the data was stored vis-a-vis
retrieval time

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