[Ovmsdev] OVMS v2 Memory/Settings Corruption

Mark Webb-Johnson mark at webb-johnson.net
Fri Nov 25 08:56:09 HKT 2016

$ perl -e 'printf "%08b\n",ord("5");'
$ perl -e 'printf "%08b\n",ord("k");'
$ perl -e 'printf "%08b\n",ord("8");'
$ perl -e 'printf "%08b\n",ord("Z");'

Strange. Seems more than a simple bit flip. I haven’t seen this myself, or heard of it much from other users.

Is the Twizy code using EEPROM for anything other than settings storage? I know that there are a very limit number of write cycles into that EEPROM space.

I did some googling, but all I can find is corruption during writing (either power down, or interrupt during write). But, for our case of very very rare EEPROM writes, that shouldn’t be an issue.

Regards, Mark.

> On 25 Nov 2016, at 5:47 AM, Michael Balzer <dexter at expeedo.de> wrote:
> The EEPROM data loss is a known issue, and I'm afraid there's nothing we can do about that. It seems to be a bug in the PIC18.
> Regards
> Michael
> Am 24.11.2016 um 22:10 schrieb Julien Banchet:
>> Hi all,
>> Thanks to Michaels last message to remind me to ask a question here:
>> Since a few months, maybe a bit more because it happens only once in a while, I have noticed I wasn't receiving the SMS alerts (feature on SMSIP mode) , and sending a "Stats?" only gave me the nasty access denied answer.
>> It turns out, using the application, I noticed that the phone number was getting corrupted (afaik, it's the only setting affected)
>> Normally: "+33651886877" it became "+336k1886877" or "+33651886Z77" etc... like a solar flare bit flip !_______________________________________________

More information about the OvmsDev mailing list