At 11:16 AM 4/9/2000 +0100, you wrote: > >you can even do a EEPROM read while the write is in > >progress. >I don't believe this is true. if so it's highly unusual and I'd expect >the data sheet to explicitly state that it is possible - my copy >doesn't. >Of course program memory can be read during the eeprom write cycle. If eeprom data memory writes are asyncronous, why would reading eeprom data memory during a write be prohibited? If it is prohibited, how would it manifest itself? Return invalid data? Halt execution until the write completed? It seems as though if any of those behaviors were true, *that* would certainly be documented. (One would hope!) - Mike > > > >Jim > > > >>Hi, > >> > >>I'd just like a confirmation on what I've gleaned from Microchip's somewhat > >>sparse notes in the datasheet regarding eeprom writes. Am I correct in > >>assuming that a write to *data* eeprom is basically asyncronous to code > >>execution, and after following their sequence to initiate a write, I can go > >>about doing other things, and will be interrupted when the write is > complete? > >> > >>Thanks... (told you it was an easy ques!) > >> > >>- Mike > >> > >Regards, > > > >Jim Robertson > >NEWFOUND ELECTRONICS > >________________________________________ > >Email: newfound@pipeline.com.au > >http://www.new-elect.com > >MPLAB compatible PIC programmers. > >________________________________________