<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I've been building and releasing using the patch already on
ovms.dexters-web.de.<br>
<br>
Toolkit -98 works perfectly in dual core mode. The last issue I had
that let me suspect it still needs unicore mode was actually the CAN
hardware flaw I reported and fixed later on.<br>
<br>
To switch to the fix:<br>
<ol>
<li>Install toolkit -98 and the newlib binaries from here: <a
href="https://github.com/espressif/esp-idf/issues/2892#issuecomment-525286663">https://github.com/espressif/esp-idf/issues/2892#issuecomment-525286663</a><a
href="https://dl.espressif.com/dl/xtensa-esp32-elf-linux64-1.22.0-98-g4638c4f-5.2.0-20190827.tar.gz"
rel="nofollow" style="box-sizing: border-box;
background-color: initial; color: rgb(3, 102, 214);
text-decoration: none;"><br>
<br>
Linux</a>
<p style="box-sizing: border-box; margin-top: 0px;
margin-bottom: 16px; color: rgb(36, 41, 46); font-family:
-apple-system, BlinkMacSystemFont, "Segoe UI",
Helvetica, Arial, sans-serif, "Apple Color Emoji",
"Segoe UI Emoji"; font-size: 14px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial;"><a
href="https://dl.espressif.com/dl/xtensa-esp32-elf-macos-1.22.0-98-g4638c4f-5.2.0-20190827.tar.gz"
rel="nofollow" style="box-sizing: border-box;
background-color: initial; color: rgb(3, 102, 214);
text-decoration: none;">MacOS</a><br style="box-sizing:
border-box;">
<a
href="https://dl.espressif.com/dl/xtensa-esp32-elf-win32-1.22.0-98-g4638c4f-5.2.0-20190827.tar.gz"
rel="nofollow" style="box-sizing: border-box;
background-color: initial; color: rgb(3, 102, 214);
text-decoration: none;">Windows</a><span> </span>(note the
Windows toolchain probably still has symlinks instead of
copies)</p>
<p style="box-sizing: border-box; margin-top: 0px;
margin-bottom: 0px !important; color: rgb(36, 41, 46);
font-family: -apple-system, BlinkMacSystemFont, "Segoe
UI", Helvetica, Arial, sans-serif, "Apple Color
Emoji", "Segoe UI Emoji"; font-size: 14px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">Also, a new set of<span> </span><a
href="https://dl.espressif.com/dl/newlib-psram-fix-ldstld-14aug.zip"
rel="nofollow" style="box-sizing: border-box;
background-color: initial; color: rgb(3, 102, 214);
text-decoration: none;">Newlib</a><span> </span>binaries,
recompiled with the above toolchain and with some manual fixes
to some assembly routines.<br>
<br>
</p>
</li>
<li>Install the newlib binaries into <tt>lib/esp32-psram</tt>,
make sure they are used by symlinking or replacing the standard
files:<br>
<tt></tt><br>
<tt><a class="moz-txt-link-abbreviated" href="mailto:balzer@leela:~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3">balzer@leela:~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3</a>>
ll
~/esp/xtensa-esp32-elf-1.22.0-98/xtensa-esp32-elf/lib/esp32-psram/<br>
insgesamt 43168<br>
-rw-r--r-- 1 balzer users 2228 13. Aug 12:52 crt0.o<br>
lrwxrwxrwx 1 balzer users 23 28. Aug 22:00 libc.a ->
libc-psram-workaround.a<br>
-rw-r--r-- 1 balzer users 5975618 14. Aug 11:25
libc-psram-workaround.a<br>
-rw-r--r-- 2 balzer users 5230008 13. Aug 12:52 libc-std.a<br>
lrwxrwxrwx 1 balzer users 23 28. Aug 22:00 libg.a ->
libg-psram-workaround.a<br>
-rw-r--r-- 1 balzer users 5985208 14. Aug 11:25
libg-psram-workaround.a<br>
-rw-r--r-- 2 balzer users 5230008 13. Aug 12:52 libg-std.a<br>
lrwxrwxrwx 1 balzer users 23 28. Aug 22:00 libm.a ->
libm-psram-workaround.a<br>
-rw-r--r-- 1 balzer users 1940568 14. Aug 11:25
libm-psram-workaround.a<br>
-rw-r--r-- 1 balzer users 2119642 13. Aug 12:52 libm-std.a<br>
-rw-r--r-- 1 balzer users 16717576 13. Aug 13:01 libstdc++.a<br>
-rw-r--r-- 1 balzer users 2286 13. Aug 13:01
libstdc++.a-gdb.py<br>
-rw-r--r-- 1 balzer users 986574 13. Aug 13:01 libsupc++.a<br>
<br>
</tt></li>
<li>Checkout branches "spiram-fix-test" on both OVMS and esp-idf.
(The esp-idf branch has the fix from <a
href="https://github.com/espressif/esp-idf/issues/2892#issuecomment-525697255">https://github.com/espressif/esp-idf/issues/2892#issuecomment-525697255</a>)</li>
<li>Disable sdkconfig:<tt>CONFIG_WIFI_LWIP_ALLOCATION_FROM_SPIRAM_FIRST</tt>
(meant to work around PSRAM issues in the wifi blob, which has
no toolkit 98 build yet)</li>
<li>make clean && make</li>
</ol>
<p>There will be some warnings about the toolkit version not
matching the idf version, these can be safely ignored.<br>
</p>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 09.12.19 um 03:09 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:8357DFD7-3A29-4771-8962-7F8A82473E64@webb-johnson.net">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Espressif have announced they're incorporating the PSRAM fix into the official toolchain now, but there is no schedule for the release.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Can you clarify what the status of this is now? What exactly do we need to switch to the fix.
Last I checked, it was only working in UNICORE mode. Have they fixed that? I see some recent commits in Espressif code referencing this, but not sure of when they plan to release.
Regards, Mark.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 27 Nov 2019, at 4:36 AM, Michael Balzer <a class="moz-txt-link-rfc2396E" href="mailto:dexter@expeedo.de"><dexter@expeedo.de></a> wrote:
Looking at the git log and changes.txt I'd say it's time to head for the next main release.
The current build with the latest changes and tiT on core 1 is working very smoothly here.
No crashes, CAN RX overflows are down to 0.25 per mille and SIMCOM overflows around 0.3 per mille.
Espressif have announced they're incorporating the PSRAM fix into the official toolchain now, but there is no schedule for the release.
Are there any open issues that need to be fixed for 3.2.006?
Regards,
Michael
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________
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>
<pre class="moz-quote-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>