<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Mark,<br>
<br>
try:
<a class="moz-txt-link-freetext" href="https://dl.espressif.com/dl/xtensa-esp32-elf-macos-1.22.0-96-g2852398-5.2.0.tar.gz">https://dl.espressif.com/dl/xtensa-esp32-elf-macos-1.22.0-96-g2852398-5.2.0.tar.gz</a><br>
<br>
…got that from here: <a
href="https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8#diff-0633a6582c888c6fc5bc6a3c00dba496R56">https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8#diff-0633a6582c888c6fc5bc6a3c00dba496R56</a><br>
<br>
But the link needs to be fixed anyway.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 16.07.20 um 13:48 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:94257C41-D9B5-4A84-90F5-43A2275F9869@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
OK. I’ve done this on the <a href="http://api.openvehicles.com"
class="" moz-do-not-send="true">api.openvehicles.com</a> build
system (Linux based). My edge build gives:
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">3.2.013-298-g025f838/ota_0/edge (build idf
v3.3.2-879-g0137aef Jul 16 2020 19:25:08)</div>
</blockquote>
<div class="">
<div class=""><br class="">
</div>
<div class="">But, the Mac osx download link gives:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">
<div class="">curl <a
href="https://dl.espressif.com/dl/xtensa-esp32-elf-osx-1.22.0-96-g2852398-5.2.0.tar.gz"
class="" moz-do-not-send="true">https://dl.espressif.com/dl/xtensa-esp32-elf-osx-1.22.0-96-g2852398-5.2.0.tar.gz</a></div>
<div class=""><html></div>
<div class=""><head><title>404 Not
Found</title></head></div>
<div class=""><body bgcolor="white"></div>
<div class=""><center><h1>404 Not
Found</h1></center></div>
<div class=""><hr><center>nginx/1.14.0
(Ubuntu)</center></div>
<div class=""></body></div>
<div class=""></html></div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>Oh, good grief. I’ll try to take it up with espressif…</div>
<div><br class="">
</div>
<div>Regards, Mark.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 16 Jul 2020, at 5:27 PM, Michael Balzer
<<a href="mailto:dexter@expeedo.de" class=""
moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div class=""> Everyone,<br class="">
<br class="">
I've merged the latest release/v3.3 esp-idf into our
idf fork and merged the PSRAM fix test branch into our
OVMS master.<br class="">
<br class="">
To build now, you need to:<br class="">
<br class="">
1. Update your toolchain to release
1.22.0-96-g2852398-5.2.0: download the toolchain for
your OS from
<a class="moz-txt-link-freetext"
href="https://docs.espressif.com/projects/esp-idf/en/release-v3.3/get-started/index.html#setup-toolchain"
moz-do-not-send="true">https://docs.espressif.com/projects/esp-idf/en/release-v3.3/get-started/index.html#setup-toolchain</a>,
simply replace your existing toolchain installation by
unpacking the archive. Test your toolchain
installation by checking xtensa-esp32-elf-gcc
--version.<br class="">
<br class="">
2. Pull our latest esp-idf master and -important-
update the submodules<br class="">
<br class="">
3. Pull/checkout our latest OVMS master<br class="">
<br class="">
4. Update your sdkconfig from
support/sdkconfig.default.hw31<br class="">
<br class="">
The build should then result in version
3.2.013-298-g025f838b/factory/edge (build idf
v3.3.2-879-g0137aef47 Jul 16 2020 10:53:38) or higher.<br
class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 15.07.20 um 08:07
schrieb Michael Balzer:<br class="">
</div>
<blockquote type="cite"
cite="mid:d6e85100-d806-297a-3aa5-3e29dc1654b5@expeedo.de"
class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
Yes, differences on the test branches are minor,
also in esp-idf. <br class="">
<br class="">
But we probably also need to pull in the latest
changes on the esp-idf 3.3 branch, which may be some
more work.<br class="">
<br class="">
I'll fetch the current toolchain version and check
what is needed.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 15.07.20 um 04:13
schrieb Mark Webb-Johnson:<br class="">
</div>
<blockquote type="cite"
cite="mid:446C1263-521A-4116-9CD0-F38ED02CFE12@webb-johnson.net"
class="">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8" class="">
Finally… Crazy that this took so long.
<div class=""><br class="">
</div>
<div class="">We have a GetOVMSHardware() in
ovms_version.cpp that picks up
the esp_chip_info_t structure and has
chip.revision (documented as "chip revision
number”). That is stored in metric m.hardware.
My bench unit is showing rev=ESP32/1. I checked
a bunch of recent cars connected to <a
href="http://api.openvehicles.com/" class=""
moz-do-not-send="true">api.openvehicles.com</a>,
but all showed the same. So not sure if the v3
silicon is not reported in that chip.revision,
if we are just using existing stocks, or an IDF
update is required to pickup the new silicon
version number. The v3 seems fairly recent
(March 2020?) and I don’t see a v2 listed.
Anyway, I’ve just yesterday received a new batch
of modules so will check those to see if it
shows up.</div>
<div class=""><br class="">
</div>
<div class="">What do we need to do to switch to
this? Presumably I turn off auto-build of the
firmware on <a
href="http://api.openvehicles.com/" class=""
moz-do-not-send="true">api.openvehicles.com</a>,
you merge your SPIRAM branch to master, we tell
everyone to download the new toolchain, then we
switch both our edge builds back to master
branch with new toolchain?</div>
<div class=""><br class="">
</div>
<div class="">Apart from the CONFIG_SPIRAM_SUPPORT
2MB workaround, I can’t see any significant
differences
between remotes/origin/spiram-fix-test and
master? Is the only difference
the ovms_websockethandler.cpp change to
std::string (vs extram::string)?</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 15 Jul 2020, at 2:11 AM,
Michael Balzer <<a
href="mailto:dexter@expeedo.de" class=""
moz-do-not-send="true">dexter@expeedo.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8"
class="">
<div class=""> Mark,<br class="">
<br class="">
it seems the fix has finally arrived in
the official release 3.3 branch:<br
class="">
<br class="">
<a
href="https://github.com/espressif/esp-idf/issues/2892#issuecomment-658327913"
class="" moz-do-not-send="true">https://github.com/espressif/esp-idf/issues/2892#issuecomment-658327913</a><br
class="">
<br class="">
<a
href="https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8"
class="" moz-do-not-send="true">https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8</a><br
class="">
<br class="">
Btw:<br class="">
<br class="">
<blockquote type="cite" class="">
<div class=" js-timeline-item
js-timeline-progressive-focus-container
"
data-gid="MDEyOklzc3VlQ29tbWVudDY0NTQyMDA5OQ=="
style="box-sizing: border-box;
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;">
<div class="js-comment-container
TimelineItem"
data-gid="MDEyOklzc3VlQ29tbWVudDY0NTQyMDA5OQ=="
data-url="/_render_node/MDEyOklzc3VlQ29tbWVudDY0NTQyMDA5OQ==/timeline/issue_comment"
style="box-sizing: border-box;
position: relative; display: flex;
padding: 16px 0px; margin-left:
16px;">
<div class="
js-minimizable-comment-group
TimelineItem-body
js-targetable-element
timeline-comment-group my-0
" id="issuecomment-645420099"
style="box-sizing: border-box;
margin-top: 4px; margin-bottom:
0px !important; min-width: 0px;
max-width: 100%; color: rgb(68,
77, 86); flex: 1 1 auto;">
<div class=" ml-n3
js-task-list-container
js-comment previewable-edit
reorderable-task-lists comment
timeline-comment
unminimized-comment
timeline-comment--caret"
data-body-version="d9e7b21e6119fab731f2490347034550"
data-unfurl-hide-url="/content_reference_attachments/hide"
style="box-sizing: border-box;
margin-left: -16px !important;
position: relative; color:
rgb(36, 41, 46);
background-color: rgb(255,
255, 255); border: 1px solid
rgb(225, 228, 232);
border-radius: 6px;">
<div class="edit-comment-hide"
style="box-sizing:
border-box;">
<table class="d-block"
data-paste-markdown-skip=""
style="box-sizing:
border-box;
border-spacing: 0px;
border-collapse: collapse;
display: block
!important;">
<tbody class="d-block"
style="box-sizing:
border-box; display:
block !important;">
<tr class="d-block"
style="box-sizing:
border-box; display:
block !important;">
<td class="
markdown-body
comment-body d-block
js-comment-body
" style="box-sizing:
border-box; padding:
15px; display: block
!important;
font-family:
-apple-system,
BlinkMacSystemFont,
"Segoe
UI", Helvetica,
Arial, sans-serif,
"Apple Color
Emoji",
"Segoe UI
Emoji";
font-size: 14px;
line-height: 1.5;
overflow-wrap:
break-word; width:
846px; overflow:
visible;">
<div
style="box-sizing:
border-box;
margin-top: 0px;
margin-bottom: 0px
!important;"
class="">In the v3
silicon, the issue
has been fixed,
and the workaround
is no longer
required.</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br class="">
I guess that means from some
manufacturing point on we should provide
two builds, one for the older hardware
and one for the modules with v3 chips,
as the fix definitely has a performance
impact.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<pre class="moz-signature" cols="72">--
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="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
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=""
moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<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="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>