I have a 08M2 low power battery-powered app that regularly naps with the normal "setfreq k31/nap 5/setfreq m32" combination.
It has "disablebod" at the start, so it runs with no brown out detection at all times.
Sometimes the batteries go very flat and need changing.
I have an
declaration in the code that almost fills the entire EEPROM - the code never writes to the EEPROM.
I have some evidence that the EEPROM is being corrupted - unfortunately the code isn't instrumented to be able to output the EEPROM values, so I can't completely prove it - but re-programming the chip sorts the problem.
Is it likely that the lack of brown out detection can lead to EEPROM corruption?
It has "disablebod" at the start, so it runs with no brown out detection at all times.
Sometimes the batteries go very flat and need changing.
I have an
Code:
eeprom 0,(0,0,0,0,0,0,0,0,0,0,50,50,50...
I have some evidence that the EEPROM is being corrupted - unfortunately the code isn't instrumented to be able to output the EEPROM values, so I can't completely prove it - but re-programming the chip sorts the problem.
Is it likely that the lack of brown out detection can lead to EEPROM corruption?