<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Answering my own question: yes, the bug has been introduced with
commit c1f96e71dd51c44f9aeff9cf5940982b939a8b24, the SPIMEM rework.<br>
<br>
Very strange…<br>
<br>
<br>
<div class="moz-cite-prefix">Am 15.06.2018 um 23:35 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:7f935a75-ca5b-783e-8abc-a8b65af6ea39@expeedo.de">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
…manifesting in "ota status" and web firmware page not being able
to show the latest version & info.<br>
<br>
It seems the error always comes on the web page.<br>
<br>
On "ota status" it normally only comes once, then successive "ota
status" calls work. Loading the web page seems to restart the
cycle.<br>
<br>
<blockquote><tt>I (695311) webserver: HTTP GET /cfg/firmware</tt><br>
<tt>W (695361) net: DNS lookup on ovms.dexters-web.de failed
err=200</tt><br>
<tt>D (695471) webserver: Serve /cfg/firmware: 9940 bytes used,
4171640 free</tt><br>
<tt>OVMS# ota status </tt><br>
<tt>Running partition: ota_1</tt><br>
<tt>Boot partition: ota_1</tt><br>
<tt>Firmware: 3.1.006-44-gd3fcb8b-dirty/ota_1/edge
(build idf ovms-3.1.006-2-g1a1a544a Jun 13 2018 23:28:20)</tt><br>
<tt>W (698871) net: DNS lookup on ovms.dexters-web.de failed
err=200</tt><br>
<tt>OVMS# ota status </tt><br>
<tt>Running partition: ota_1</tt><br>
<tt>Boot partition: ota_1</tt><br>
<tt>Firmware: 3.1.006-44-gd3fcb8b-dirty/ota_1/edge
(build idf ovms-3.1.006-2-g1a1a544a Jun 13 2018 23:28:20)</tt><br>
<tt>Server Available: 3.1.006-45-gd8220ef (is newer)</tt><br>
<br>
<tt>OTA bleeding edge developer build Wed Jun 13 23:54:42 CEST
2018</tt><br>
<tt>See ovms3.log for details</tt><br>
<br>
<tt>d8220ef - Web UI: simplified time zone region selection
(vehicle config)</tt><br>
<tt>d3fcb8b esp32can: Try draining rx fifo in main
ESP32CAN_rxframe function</tt><br>
</blockquote>
<br>
This is brand new, has been working flawlessly before. Mark, can
this be caused by the aggressive SPIMEM rework?<br>
<br>
Regards,<br>
Michael<br>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>