<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-15">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Please note: a "git pull" will not work
to update your local esp-idf.<br>
<br>
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>
<br>
A fresh clone is always an option, but resyncing your local master
branch to origin/master should do as well:<br>
<blockquote><tt>git fetch</tt><br>
<tt>git checkout -fB master origin/master</tt><br>
<tt>git submodule update --recursive</tt><br>
</blockquote>
<br>
Regards,<br>
Michael<br>
<br>
<br>
Am 21.07.19 um 21:33 schrieb Michael Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:58a4d922-dca3-be4c-17d8-00279bdaa53f@expeedo.de">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-15">
Update is pushed.<br>
<br>
Don't forget to do a submodule update in the esp-idf, I also
recommend doing a "make clean" before the next build.<br>
<br>
Use the defaults for new config options, except:<br>
- disable SPIRAM_BANKSWITCH_ENABLE (bank switching for >4MiB
external RAM)<br>
- disable FATFS_ALLOC_PREFER_EXTRAM (Perfer external RAM when
allocating FATFS)<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 20.07.19 um 23:21 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:7cbe382e-53f3-22ca-08f6-40d8cfbabea2@expeedo.de">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-15">
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>
<br>
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>
<br>
So I merged v3.3 directly afterwards, and that builds without
issues.<br>
<br>
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>
<blockquote><tt>OVMS# wifi mode off </tt><br>
<tt>Stopping wifi station...</tt><br>
<tt>I (1307252) esp32wifi: Stopping WIFI station</tt><br>
<tt>I (1307252) netmanager: Interface priority is pp3
(10.170.195.13/255.255.255.255 gateway 10.64.64.64)</tt><br>
<tt>I (1307252) netmanager: Set DNS#2 0.0.0.0</tt><br>
<tt>I (1307252) netmanager: WIFI client down (with MODEM up):
reconfigured for MODEM priority</tt><br>
<tt>I (1307252) wifi: state: run -> init (0)</tt><br>
<tt>I (1307262) wifi: pm stop, total sleep time: 1100678913 us
/ 1301859253 us</tt><br>
<tt>I (1307262) wifi: new:<1,0>, old:<1,1>,
ap:<1,1>, sta:<1,0>, prof:1</tt><br>
<tt>E (1307262) event:
system_event_sta_disconnected_handle_default 294
esp_wifi_internal_reg_rxcb ret=0x3014</tt><br>
<tt>E (1307262) event: system_event_ap_stop_handle_default 223
esp_wifi_internal_reg_rxcb ret=0x3014</tt><br>
<tt>W (1307262) netmanager: CleanupConnections: can't get AP
station list</tt><br>
<tt>I (1307272) wifi: flush txq</tt><br>
<tt>I (1307272) wifi: stop sw txq</tt><br>
<tt>I (1307272) wifi: lmac stop hw txq</tt><br>
<tt>I (1307292) time: Network was reconfigured: restarting
SNTP client</tt><br>
<tt>I (1307322) netmanager: Set DNS#2 0.0.0.0</tt><br>
<tt>I (1307322) esp32wifi: STA disconnected with reason 8</tt><br>
<tt>I (1307352) netmanager: Set DNS#2 0.0.0.0</tt><br>
<tt>I (1307392) netmanager: Set DNS#2 0.0.0.0</tt><br>
<tt>I (1307392) netmanager: WIFI access point is down</tt><br>
<tt>I (1307392) esp32wifi: AP stopped</tt><br>
<tt>OVMS# net status </tt><br>
<tt>Interface#3: pp3 (ifup=1 linkup=1)</tt><br>
<tt> IPv4: 10.170.195.13/255.255.255.255 gateway 10.64.64.64</tt><br>
<br>
<tt>Interface#2: ap2 (ifup=1 linkup=1)</tt><br>
<tt> IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1</tt><br>
<br>
<tt>DNS: 192.168.2.1 192.168.2.1</tt><br>
<br>
<tt>Default Interface: pp3 (10.170.195.13/255.255.255.255
gateway 10.64.64.64)</tt><br>
<tt>OVMS# </tt><br>
</blockquote>
<br>
But wifi is off, and after starting the wifi network again,
everything works, so that's a minor issue.<br>
<br>
I'll do some more tests tomorrow, then push the update.<br>
<br>
Regards,<br>
Michael<br>
<br>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="144">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>