??? 08/14/07 19:12 Read: times |
#143281 - this depends on application, too Responding to: ???'s previous message |
Kai Klaas said:
Also, how to notice a data corruption if you cannot access the BBRAM because you block it via the !CS input?? If you wanted to write "FF" and you read "FF" afterwards, is it the correct BBRAM content or the level caused by the micro's internal pull-ups as consequence of a blocked BBRAM? With some smart thinking, this is manageable, too (double-copy of a set of parameters, with indication of age and checksum, for example). Again, this depends on the particular application. There are applications, where write to NVRAM is ocassional only, and such events are tolerable if detected. JW |