<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi list,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Another quick post to share with you
the progress on the ESP-IDFv5 + cmake endeavour:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
<ul>
<li>ESP-IDF v5 version of OVMSv3 is now officially booting and
seems to work fine (then again, I'm not doing any real-world
testing for lack of time / car at the moment - it's here that
you can help me) with a few caveats detailed in the PR or <a
moz-do-not-send="true"
href="https://github.com/llange/Open-Vehicle-Monitoring-System-3/blob/experimental-esp-idf-v5/README.md">the
README.md</a>.<br>
<br>
</li>
<li>The branch
<a class="moz-txt-link-freetext" href="https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v5">https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v5</a>
is now ready for testing, sharing, studying, ...<br>
<br>
</li>
<li>I created a draft PR
<a class="moz-txt-link-freetext" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/810">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/810</a>
(just like for ESP-IDFv4), in order to show the diff and
gather feedback. Not to be merged as-is.<br>
<br>
</li>
<li>I'll try to break it into smaller low-impact /
easy-to-review PR's that could be merged as-is in current
master (warning corrections, header definitions, xxprintf type
impact, etc...), so that the big pieces could be more easily
reviewed.<br>
</li>
</ul>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please note that those branches / PRs
are still Work-In-Progress, and that I may certainly (and wrongly)
`push --force` some changes as I rebase, update or split the big
PR into smaller, easy to study PRs. I'll try not to but can't
promise :-)</div>
<div class="moz-cite-prefix">So if you checkout the branch, please
be warned and know your git commands to either reset or rebase
your working copy...<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Next on my list are, in no particular
order:</div>
<div class="moz-cite-prefix">
<ul>
<li>Have a few patches/bugs fixed in upstream wolfSSL (in
progress) in order to enable<br>
</li>
<li>Check to see if we could upgrade mongoose (not absolutely
necessary because it works / compile OK with a small patch)</li>
<li>Fix the remaining warnings</li>
<ul>
<li>And change the ADC implementation that is deprecated now</li>
<li>deprecation of esp_vfs_fat_spiflash_mount /
esp_vfs_fat_spiflash_unmount</li>
</ul>
<li>Fix the WIP WIP WIP commits</li>
<li>Resume work on
<a class="moz-txt-link-freetext" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/752">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/752</a><br>
</li>
</ul>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Boot time warnings to study and check
if OK:</div>
<div class="moz-cite-prefix">
<ul>
<li>W (1091) esp_psram: Virtual address not enough for PSRAM,
map as much as we can. 4MB is mapped</li>
<li>W (2132) ADC: legacy driver is deprecated, please migrate to
`esp_adc/adc_oneshot.h` (<- this one is easy to
understand...)</li>
</ul>
<p><br>
</p>
<p>Additional instructions:</p>
<p>When first building, your sdkconfig will be converted as some
config options did change betwen ESP-IDF v3.x and v5.x.</p>
<p>Run `menuconfig` and :</p>
<ul>
<li><b>Select FREERTOS_ENABLE_BACKWARD_COMPATIBILITY</b>(=y)
"configENABLE_BACKWARD_COMPATIBILITY"</li>
<li><b>Unselect MG_ENABLE_SSL</b>(=n) "Enable MONGOOSE SSL/TLS
support"</li>
</ul>
<p><br>
</p>
<p>If any of you with some free time could be nice enough to try
to reproduce such a build and share the experience here. Let me
know how the instructions could be updated and what issues you
are facing.<br>
</p>
<p><br>
</p>
</div>
<div class="moz-cite-prefix">Best regards,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 27/01/2023 à 03:17, Michael Geddes a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAH0p7uJJW5sH8L1tWgxF0sHo+Ov_HZxeozWrxtRR9EOuVv+jSg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">I may try this on my spare board as a start! (The
Aux 12v switch didn't work... But otherwise it's mostly OK)
<div dir="auto"><br>
</div>
<div dir="auto">Michael. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 26 Jan 2023, 4:41 pm
Mark Webb-Johnson, <<a href="mailto:mark@webb-johnson.net"
moz-do-not-send="true" class="moz-txt-link-freetext">mark@webb-johnson.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="line-break:after-white-space">Progress looks good
on this. Thanks for stepping up to try to tackle it.
<div><br>
</div>
<div>Pain points for me with our current approach are:</div>
<div><br>
</div>
<div>
<ol>
<li>RAM usage (in particular IRAM)</li>
<li>IDF bugs that may be improved in newer versions</li>
<li>Support for newer hardware (including ESP32-S3)</li>
</ol>
<div><br>
</div>
<div>#3 would give us a welcome 12 more GPIOs with minimal
hardware changes, but possibly worse RAM situation
(520KB->512KB, see #1).</div>
<div><br>
</div>
<div>My preference would be v5 IDF (for the newer hardware
support).</div>
<div><br>
</div>
<div>I think it would be fine to have this as a new
branch. Not particularly important to make it work in
the master one.</div>
<div><br>
</div>
<div>Regards, Mark.</div>
<div><br>
<blockquote type="cite">
<div>On 26 Jan 2023, at 8:56 AM, Ludovic LANGE <<a
href="mailto:ll-ovmsdev@lange.nom.fr"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">ll-ovmsdev@lange.nom.fr</a>>
wrote:</div>
<br>
<div>
<div>
<div>Hi,</div>
<div><br>
</div>
<div>A quick note to share with you the progress
on the ESP-IDFv4 + cmake endeavour:</div>
<div>
<ul>
<li>The branch
<a
href="https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v4-rework-network"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v4-rework-network</a>
is now ready for greater review. Most of the
warnings are gone, and I'll need some help
for the last ones.<br>
<br>
</li>
<li>I created a draft PR
<a
href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/806"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/806</a>
. Not that I want to merge it as-is nor
soon, but it may help the review process to
have some central discussion point.<br>
<br>
</li>
<li>I'll now switch to ESP-IDFv5 porting - on
a new branch (based on the v4) :
<a
href="https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v5"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v5</a>
(empty at the moment).<br>
</li>
</ul>
</div>
<div><br>
</div>
<div>Regards,<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>