Re: What is preferable for storing parameters FLASH or on-chip EEPROM ?

Hi Peter,
My approach is to be flexible whether I want to update all 30 bytes
or just some of them or even one byte.As most log parameters are
int ( 2 bytes) , updating only one parameter will result in writing
2 bytes.If using EEPROM any byte writing will result in factor *10msec.
Data log array ends with checksum on all data, so updating any
of parameters in the block results that the checksum must be
recalculated and updated too.

Reading the Flash bytes is very quickly, I think it is the same
as reading from EEPROM so reading log data is not the issue.

In case when using Flash,'read modify write' method may be
performed by reading even all 30 bytes, changing whatever
needed and then writing back all data in 10 msec.

Important to note that log data holds errors which occured
in the system,they are not so frequent so there is no
question of reaching the 100k write cycles limit at all.

In the supplied by Atmel write_flash(address, buffer , size)
function,the size parameter is how many bytes to program.
If size=1 only one byte is programmed leaving all remaining
bytes of the same page in Flash unchanged.
I hope that Atmel's programming algorithm does not reprogram
the remaining bytes of this page with the same data.
So lifetime and 100k write cycles limit is the same regarding
page or byte writing.

I am still thinking that using FLASH is preferable than using
EEPROM in this case.

What do you think?

The question is whether there exist any other problems in using
Flash which I currently don't see.I didn't make the coding yet
so your advice may be helpful to me.
Regards.

.