<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Eddy,<br>
<br>
note that Fabrizio works on porting the OVMS to ESP-IDF 4:<br>
<br>
<a
href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/263#issuecomment-606132473">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/263#issuecomment-606132473</a><br>
<br>
Maybe you can join forces?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 08.04.20 um 04:05 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:81F8AA0D-48E9-4B58-A538-F65DA4BFDA62@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class=""><br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div id="Signature" class="">Am I correct to assume that the
16Mb of memory is on the module now?</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
The ESP32 chip uses an external flash chip. The WROOM/WROVER
modules include a flash chip in the modules.
<div class=""><br class="">
</div>
<div class="">In the very early days of development prototypes for
OVMS v3, we used an external 16MB flash chip (as only 4MB WROOM
modules were available at the time).</div>
<div class=""><br class="">
</div>
<div class=""><font class="" color="#000000"><span
style="caret-color: rgb(0, 0, 0);" class="">For production,
we switched to 16MB WROVER modules, so don’t require any
external flash chip any more.</span></font></div>
<div class=""><font class="" color="#000000"><span
style="caret-color: rgb(0, 0, 0);" class=""><br class="">
</span></font></div>
<div class="">
<blockquote type="cite" class="">
<div class="">
<div id="Signature" class="">How are the core developers
dealing with this slowness?</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
I don’t find it slow at all (but I use MAC and LINUX for
development). Most of the time, it is an incremental build (only
building changes code, and then a linking step) - it normally
takes longer to flash the chip than build the code. I timed a
full ‘make clean; make -j 4’ to see what it is for me:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">$ time make -j 4</div>
<div class="">...</div>
<div class="">
<div class="">real<span class="Apple-tab-span" style="white-space:pre"> </span>2m53.557s</div>
<div class="">user<span class="Apple-tab-span" style="white-space:pre"> </span>5m55.978s</div>
<div class="">sys<span class="Apple-tab-span" style="white-space:pre"> </span>1m40.391s</div>
</div>
</blockquote>
<div class="">
<div><br class="">
</div>
<div>Just under 3 minutes real time. Perhaps you can check in
windows to see how much worse it is?</div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div id="Signature" class="">Is it at all possible, if i
could force platformio to use the correct the idf-esp
libraries, to compile the OVMS code in a more recent
environment that uses cmake and ninja?</div>
</div>
</blockquote>
</div>
<div><br class="">
</div>
<div>I haven’t tried it myself. We do have some make scripts in
various components that may rely on the existing build system.
Things like the versioning.</div>
<div><br class="">
</div>
<div>OVMS was written when ESP-IDF was quite new, and
unpolished. At some point, we will most likely migrate to a
newer build system, as ESP-IDF matures.</div>
<div><br class="">
</div>
<div>Regards, Mark.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 8 Apr 2020, at 8:37 AM, Eddy Vromen <<a
href="mailto:eddy_vromen@hotmail.com" class=""
moz-do-not-send="true">eddy_vromen@hotmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<div style="font-family: Calibri, Helvetica, sans-serif;
font-size: 12pt;" class=""><br
class="Apple-interchange-newline">
<br class="">
</div>
<div id="Signature" class=""><br class="">
HI All,</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class="">I have a question about the
flash memory of the ESP32.</div>
<div id="Signature" class="">I read that the ESP32 uses
16Mb of external flash memory and in the schematics on
page 27 there is a flash memory chip. However, in the
latest v3.2 schematics there is no external flash
chip.</div>
<div id="Signature" class="">Am I correct to assume that
the 16Mb of memory is on the module now?</div>
<div id="Signature" class="">How does this impact the
e-fuse settings?</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class="">Another question that came
up while setting up a development environment:</div>
<div id="Signature" class="">The version of esp-idf
thats used by the OVSM project uses the Mingw32
environment. Based on my limited exposure to using
this environment, its very slow compared to compiling
esp-idf code under e.g. platformio under VSCode. </div>
<div id="Signature" class="">How are the core developers
dealing with this slowness?</div>
<div id="Signature" class="">Is it at all possible, if i
could force platformio to use the correct the idf-esp
libraries, to compile the OVMS code in a more recent
environment that uses cmake and ninja?</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class=""><br class="">
</div>
<div id="Signature" class="">Thanks,</div>
<div id="Signature" class="">Eddy<br class="">
<br class="">
</div>
</div>
<span style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">_______________________________________________</span><br
style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">OvmsDev mailing list</span><br
style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<a href="mailto:OvmsDev@lists.openvehicles.com"
style="font-family: Helvetica; font-size: 18px;
font-style: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;" class=""
moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 18px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<a
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
style="font-family: Helvetica; font-size: 18px;
font-style: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;" class=""
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</blockquote>
</div>
<br class="">
</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="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>