When performing the programming (byte, word, block) on flash program memory the
CPU is frozen until the end of programming EOP after that the CPU resume
processing but when performing the programming operation on data eeprom the CPU
is frozen until the end of high voltage HVOFF.
So, Volkan code taking advantages of RWW feature as don’t waiting the EOP flag
for(i=0; i<ARRAYSIZE; i++, add++)
SET); // should be deleted to take advantage of
When performing operation on data eeprom and taking advantage of RWW feature
(the time between the HVOFF and EOP) we can also performing another write
operation on data eeprom.
The CPU is frozen does mean that can not perform any operation until the end of
the current operation (can't execute from program flash) when performing
write operation on data eeprom the frozen phase finished after the end of high
voltage HVOFF(~1,7ms) then the CPU resume processing (RWW feature). The EOP
flag is set after (~3ms), this feature not exist on flash program memory
the frozen phase finished after the end of programming EOP. When interrupt occured
during frozen phase will be delayed until CPU resume processing
I agree with you that the CPU will be frozen for each byte programming (when
call the programming byte muli-times the cpu each time resume processing after
write the byte n then goes back frozen when trying to write the byte n+1
;) ) just I want to add that this code benefit for the RWW feature (to program
10 byte without rww feature the operation take 3ms x10 and with rww feature the
operation take ~1.7ms x10)
Retrieving data ...