>=20
> I don't see a problem here since you shouldn't be attempting to read the
> EEPROM while a write is in progress.

 Nowhere where I read it does it say that you're not allowed to do this. An=
d=20
on the 16F628, it works.

> This is a rather unfortunate difference,
>=20
> No, just unfortunate programming.

 I would call it "squeezing all out of a PICmicro that is in it". Yesterday=
=20
I spent two hours trying to find a way to reduce a piece of code by one=20
instruction, so I would have enough time to do a proper clrf on PCLATH=20
before shifting values in it (I wanted to use my program on the 16F688, and=
=20
because of its larger memory the contamination in the top bits of PCLATH=20
caused it to fail). I don't think there is any time for me to add another=
=20
instruction in the loop to check whether I am writing to the EEPROM and not=
=20
read from it. Calling it unfortunate programming before you know what I am=
=20
doing... Well, it just hurts.
 Yes, the code uses very ugly shortcuts. I use input variables and jump to=
=20
fixed locations in memory based on them. I require that 90% of the variable=
s=20
in the first two banks are in a fixed location, as they are directly=20
accessible through RS-232. However, it is able to do stuff that I doubt=20
would be possible if I did keep the code neat.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist