>  I debugged for a while, and then I discovered that the 16F628A doesn't
>allow you to read the EEPROM while it is writing to it. On the 16F628, if
>you read the EEPROM while writing to it, it returns 0xFF and writes the
>correct value. On the 16F628A, if you read the EEPROM while writing to it,
>it returns 0xFF but also stores 0xFF into it, instead of the requested
>value. This is a rather unfortunate difference, which is why I decided to
>let you know.

Consider reading the 16F628A errata document. It won't make you happy but 
at least will explain things a bit.

Josef


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist