<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Michael,</div><div class=""><br class=""></div><div class="">Some comments / questions:</div><div class=""><br class=""></div>Works ok for me. But I still got a mess in esp-idf (submodules not updated, old dependency .d files still around, etc), so had to remove it and re-clone.<div class=""><br class=""><div class="">Builds identify as:<span class="Apple-tab-span" style="white-space:pre"> </span>3.2.002-141-g1dc82dd/ota_1/edge (build idf v3.1-dev-4770-ge97f72e Jul 22 2019 19:25:36)<br class=""><div><br class=""></div><div>Is that correct? 3.1-dev-4770? Should it not be 3.3?</div><div><br class=""></div><div>Bluetooth is not building for me, so I disabled it for the moment (it wasn’t enabled on the main build server anyway - just local development). Better to let espresso stabilise first before trying that again - just too many bugs and idiosyncratic behaviour.</div><div><br class=""></div><div>What is the current status of the toolchain with the PSRAM memory corruption fix? I see they released a newer version but you said it caused endless boot loop? Are you still running the version before that? Any point for us to change our public build system to it?</div><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 22 Jul 2019, at 3:04 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-15" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Please note: a "git pull" will not work
to update your local esp-idf.<br class="">
<br class="">
I had to reset the master branch to a previous commit to undo the
revert of the last update attempt. So origin/master is now
basically a new branch.<br class="">
<br class="">
A fresh clone is always an option, but resyncing your local master
branch to origin/master should do as well:<br class="">
<blockquote class=""><tt class="">git fetch</tt><br class="">
<tt class="">git checkout -fB master origin/master</tt><br class="">
<tt class="">git submodule update --recursive</tt><br class="">
</blockquote>
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 21.07.19 um 21:33 schrieb Michael Balzer:<br class="">
</div>
<blockquote type="cite" cite="mid:58a4d922-dca3-be4c-17d8-00279bdaa53f@expeedo.de" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-15" class="">
Update is pushed.<br class="">
<br class="">
Don't forget to do a submodule update in the esp-idf, I also
recommend doing a "make clean" before the next build.<br class="">
<br class="">
Use the defaults for new config options, except:<br class="">
- disable SPIRAM_BANKSWITCH_ENABLE (bank switching for >4MiB
external RAM)<br class="">
- disable FATFS_ALLOC_PREFER_EXTRAM (Perfer external RAM when
allocating FATFS)<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 20.07.19 um 23:21 schrieb Michael
Balzer:<br class="">
</div>
<blockquote type="cite" cite="mid:7cbe382e-53f3-22ca-08f6-40d8cfbabea2@expeedo.de" class="">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-15" class="">
FYI: I've merged the current v3.3 status and am now running the
new build (toolchain still 1.22.0-93-gf6c4cdf) on my modules.<br class="">
<br class="">
I though it would be easier to merge v3.2 first, but that didn't
work out. The current v3.2 status seems to have a bug, it
wouldn't link due to too many segments. The segments have been
introduced by a wifi blob update to support a new wifi IRAM
optimization, but that needs a linker script & esptool
update as well, that seems to be available only in the v3.3
branch.<br class="">
<br class="">
So I merged v3.3 directly afterwards, and that builds without
issues.<br class="">
<br class="">
So far I haven't noticed any relevant problems running the new
build. On stopping the wifi module, two event errors get logged,
and the AP network interface remains configured as up:<br class="">
<blockquote class=""><tt class="">OVMS# wifi mode off </tt><br class="">
<tt class="">Stopping wifi station...</tt><br class="">
<tt class="">I (1307252) esp32wifi: Stopping WIFI station</tt><br class="">
<tt class="">I (1307252) netmanager: Interface priority is pp3
(10.170.195.13/255.255.255.255 gateway 10.64.64.64)</tt><br class="">
<tt class="">I (1307252) netmanager: Set DNS#2 0.0.0.0</tt><br class="">
<tt class="">I (1307252) netmanager: WIFI client down (with MODEM up):
reconfigured for MODEM priority</tt><br class="">
<tt class="">I (1307252) wifi: state: run -> init (0)</tt><br class="">
<tt class="">I (1307262) wifi: pm stop, total sleep time: 1100678913 us
/ 1301859253 us</tt><br class="">
<tt class="">I (1307262) wifi: new:<1,0>, old:<1,1>,
ap:<1,1>, sta:<1,0>, prof:1</tt><br class="">
<tt class="">E (1307262) event:
system_event_sta_disconnected_handle_default 294
esp_wifi_internal_reg_rxcb ret=0x3014</tt><br class="">
<tt class="">E (1307262) event: system_event_ap_stop_handle_default 223
esp_wifi_internal_reg_rxcb ret=0x3014</tt><br class="">
<tt class="">W (1307262) netmanager: CleanupConnections: can't get AP
station list</tt><br class="">
<tt class="">I (1307272) wifi: flush txq</tt><br class="">
<tt class="">I (1307272) wifi: stop sw txq</tt><br class="">
<tt class="">I (1307272) wifi: lmac stop hw txq</tt><br class="">
<tt class="">I (1307292) time: Network was reconfigured: restarting
SNTP client</tt><br class="">
<tt class="">I (1307322) netmanager: Set DNS#2 0.0.0.0</tt><br class="">
<tt class="">I (1307322) esp32wifi: STA disconnected with reason 8</tt><br class="">
<tt class="">I (1307352) netmanager: Set DNS#2 0.0.0.0</tt><br class="">
<tt class="">I (1307392) netmanager: Set DNS#2 0.0.0.0</tt><br class="">
<tt class="">I (1307392) netmanager: WIFI access point is down</tt><br class="">
<tt class="">I (1307392) esp32wifi: AP stopped</tt><br class="">
<tt class="">OVMS# net status </tt><br class="">
<tt class="">Interface#3: pp3 (ifup=1 linkup=1)</tt><br class="">
<tt class=""> IPv4: 10.170.195.13/255.255.255.255 gateway 10.64.64.64</tt><br class="">
<br class="">
<tt class="">Interface#2: ap2 (ifup=1 linkup=1)</tt><br class="">
<tt class=""> IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1</tt><br class="">
<br class="">
<tt class="">DNS: 192.168.2.1 192.168.2.1</tt><br class="">
<br class="">
<tt class="">Default Interface: pp3 (10.170.195.13/255.255.255.255
gateway 10.64.64.64)</tt><br class="">
<tt class="">OVMS# </tt><br class="">
</blockquote>
<br class="">
But wifi is off, and after starting the wifi network again,
everything works, so that's a minor issue.<br class="">
<br class="">
I'll do some more tests tomorrow, then push the update.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
</blockquote>
</blockquote>
<br class="">
<pre class="moz-signature" cols="144">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></div></body></html>