In all of the Microchip datasheets, Special Microcontroller Features are listed such as the typical number of erase/write cycles EEPROM data memory can handle.
What happens if this number of read/write cycles is exceeded in the lifetime of the PIC? Does the EEPROM data simply become unreliable or does it actually have a direct influence on the total operation of the PIC?
I have an application where I keep record of an electrical motors number of starts and runtime (in seconds). I store the data every single second while the motor is running.
In the case of the PIC16F88, the typical EEPROM number of cycles is 1,000,000. That gives me a total runtime of about 11.57 days (1,000,000/3600/24).
I’m quite anxious to see what’s going to happen one of these days. (Like they always ask in Brainiac, “will it float or will it sink”)![Big Grin :D :D](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
What happens if this number of read/write cycles is exceeded in the lifetime of the PIC? Does the EEPROM data simply become unreliable or does it actually have a direct influence on the total operation of the PIC?
I have an application where I keep record of an electrical motors number of starts and runtime (in seconds). I store the data every single second while the motor is running.
In the case of the PIC16F88, the typical EEPROM number of cycles is 1,000,000. That gives me a total runtime of about 11.57 days (1,000,000/3600/24).
I’m quite anxious to see what’s going to happen one of these days. (Like they always ask in Brainiac, “will it float or will it sink”)