<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:"Consolas",serif;
color:black;}
span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=FR-CH style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Sorry! Did not had time to flash. </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Will do it this week.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Pierre<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>Von:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] <b>Im Auftrag von </b>Michael Balzer<br><b>Gesendet:</b> Sonntag, 11. Dezember 2016 08:58<br><b>An:</b> ovmsdev@lists.teslaclub.hk<br><b>Betreff:</b> Re: [Ovmsdev] OVMS v2 Memory/Settings Corruption<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Got the buffer overrun effect yesterday with the new release.<br><br>As I now...<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>- Keep volatile features over reset<o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><br>...it now also shows up with random data in features 0-7. Annoying.<br><br>Julien, Pierre, any crash debug data collected yet?<br><br>Regards,<br>Michael<br><br><o:p></o:p></p><div><p class=MsoNormal>Am 29.11.2016 um 22:13 schrieb Julien Banchet:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><div><p class=MsoNormal>Thank you Michael,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Will flash it this weekend!<o:p></o:p></p></div><p class=MsoNormal>MfG,<o:p></o:p></p></div><p class=MsoNormal>JaXX./.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Nov 29, 2016 at 10:10 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" target="_blank">dexter@expeedo.de</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>Julien, Pierre,<br><br>here's a firmware build with crash debug enabled:<br><a href="https://dexters-web.de/f/tw-beta/OVMS-Twizy-3.8.2-crashdebug.zip" target="_blank">https://dexters-web.de/f/tw-beta/OVMS-Twizy-3.8.2-crashdebug.zip</a><br><br>It excludes the diag mode (serial interface command shell) but is otherwise complete.<br><br>The crash debug logs to the server (when it is/becomes available), historical record type "*-OVM-DebugCrash". These records expire after 30 days, so you can collect some days.<br><br>The crash count and data from the most recent crash will also be shown by the SMS/text command "DIAG".<br><br>The crash records contain a crash count, crash reasons (flags from RCON) and the last checkpoint seen before the crash.<br><br>Regards,<br>Michael <o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><o:p></o:p></p><div><p class=MsoNormal>Am 28.11.2016 um 22:37 schrieb Julien Banchet:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Sure Michael,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>I've never got around compiling it right, and I'm out of a Windows since, wow, I don't even know if grub would boot the partition anymore... If you have it under hand (i hope), I'd be happy to give it a shot, it would also be the occasion for me next weekend to pull a ribbon cable out once and for all (or find a clever way to keep it hidden though programmable)<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>How does crash recording work ? over Diag ? (PS: 50M/month data if needed)<o:p></o:p></p></div><p class=MsoNormal>Julien<br>./.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Nov 28, 2016 at 10:16 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" target="_blank">dexter@expeedo.de</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>There's no memory management in the module, there's too few RAM available to do dynamic allocations.<br><br>All buffers are static, the error can be some pointer corruption or missing length check / end of string check.<br><br>A stack overflow could also be possible, the software stack is 256 bytes (1 page). As there's not enough ROM left to support the crash debug framework anymore in the Twizy build, I cannot tell if that happens again.<br><br>Julien, you could try a reduced build with crash debug recording enabled...<br><br>Regards,<br>Michael <o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><o:p></o:p></p><div><p class=MsoNormal>Am 28.11.2016 um 22:00 schrieb Greg D.:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>Ah! That sounds much more likely.<br><br>Is there an error (timeout) path that might be freeing the buffer when it's still in use?<br><br>Greg.<br><br><o:p></o:p></p><div><p class=MsoNormal>Michael Balzer wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Greg, welcome :)<br><br>Juliens parameter #0 has been overwritten with "Topping o", which is part of the charge status message ("Topping off").<br><br>So it's much more likely we've got a buffer corruption bug that's triggered by (maybe) bad connectivity situations.<br><br>Regards,<br>Michael<br><br><o:p></o:p></p><div><p class=MsoNormal>Am 28.11.2016 um 06:38 schrieb Greg D.:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>Hi all,<br><br>New here, so this may be totally off the wall.<br><br>I notice that the first example, with a "5" going to a "k", it may be more easily explained as a bit <b><i>shift</i></b> instead of a set of flips. Is there anywhere in the system where the bytes are clocked serially between devices, where there may be some marginal timing?<br><br>Just a thought.<br><br>Greg.<br><br><o:p></o:p></p><div><p class=MsoNormal>Mark Webb-Johnson wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>$ perl -e 'printf "%08b\n",ord("5");'<o:p></o:p></pre><pre>00110101<o:p></o:p></pre><pre>$ perl -e 'printf "%08b\n",ord("k");'<o:p></o:p></pre><pre>01101011<o:p></o:p></pre><pre>$ perl -e 'printf "%08b\n",ord("8");'<o:p></o:p></pre><pre>00111000<o:p></o:p></pre><pre>$ perl -e 'printf "%08b\n",ord("Z");'<o:p></o:p></pre><pre>01011010<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Strange. Seems more than a simple bit flip. I haven’t seen this myself, or heard of it much from other users.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Regards, Mark.<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>On 25 Nov 2016, at 5:47 AM, Michael Balzer <a href="mailto:dexter@expeedo.de" target="_blank"><dexter@expeedo.de></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Regards<o:p></o:p></pre><pre>Michael<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Am 24.11.2016 um 22:10 schrieb Julien Banchet:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi all,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks to Michaels last message to remind me to ask a question here:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>It turns out, using the application, I noticed that the phone number was getting corrupted (afaik, it's the only setting affected)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Normally: "<a href="tel:%2B33651886877" target="_blank">+33651886877</a>" it became "+336k1886877" or "+33651886Z77" etc... like a solar flare bit flip !_______________________________________________<o:p></o:p></pre></blockquote></blockquote><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<o:p></o:p></pre><pre>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<o:p></o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<o:p></o:p></pre><pre>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<o:p></o:p></pre></div></div></div><p class=MsoNormal>_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a> <a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> <o:p></o:p></p></blockquote></div></div><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<o:p></o:p></pre><pre>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<o:p></o:p></pre></div></div></div><p class=MsoNormal>_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a> <a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> <o:p></o:p></p></blockquote></div></div><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><o:p></o:p></pre><pre><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<o:p></o:p></pre><pre>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<o:p></o:p></pre></div></body></html>