I don't think so. If I was the manufacturer, I would implement each non-volatile Block Protect bit by a larger number of non-volatile memory bits and take the average of all these when reading "its" content. This would make sense as the Block Protect bits are way more often altered than any other non-volatile memory bit.


This can have many reasons. For instance to distinguish between a data storage memory that is altered all the time and an important configuration data section which is only altered rarely.

Remember that the reset performance of your micro has a major influence, when thinking about memory security. Don't trust too much the hardware protection of EEPROM, but spend the micro a good reset controller and use the watchdog feature. A MAX1232 providing an external brown-out detection and containig a watchdog is a good choice.

Also, remember that fast glitches on any pin of micro can make the program counter jump to undefined code lines eventually unlocking the software protection. So, your micro must be extremely well shielded against all kind of EMI.

Kai Klaas