<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Michael,<br>
Hi list,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thanks Michael for having taken the
time to reproduce the build, and thus making this branch go from
the state of "urban legend" to "has been confirmed at least once"
:-)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I hope more of you will be able to
follow the instructions of Michael, that are very clear and should
ease your work when wanting to test this branch.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Ideally, I wanted that some of you
having both the time (...) and a vehicle to test would be able to
use this build as a daily driver, hoping that the known missing
parts would not be a showstopper. Let me know, and also if you
have some spare cycles you can check
<a class="moz-txt-link-freetext" href="https://github.com/wolfSSL/wolfssl/issues/6028">https://github.com/wolfSSL/wolfssl/issues/6028</a> in order to help
fix some remaining issues on this library we depend on.<br>
</div>
<p>In the meantime, I believe we can try to integrate (part of) this
branch in master. I already started to distillate some parts of
this in multiples MRs here
<a class="moz-txt-link-freetext" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pulls?q=is%3Aopen+is%3Apr+author%3Allange+draft%3Afalse">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pulls?q=is%3Aopen+is%3Apr+author%3Allange+draft%3Afalse</a>
; which could be merged without -I hope, but the review will
confirm- any impact nor regression to the current master branch.<br>
</p>
<div class="moz-cite-prefix">Let me know if I should continue in
that direction, and sorry for sounding impatient about it :-)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Regards,<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 18/02/2023 à 10:12, Michael Balzer a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:1b4278c4-38de-dfcd-051d-a8481b19d5b4@expeedo.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Ludovic,<br>
<br>
the issue is bound to the docker image version, I was using
"espressif/idf", which is "latest".<br>
<br>
The build works using the same sdkconfig with
"espressif/idf:release-v5.0" (and again fails at that mbedtls
module when switching back to the "latest" image).<br>
<br>
So to build the current experimental state, I recommend using the
docker image and basically doing the steps Ludovic formalized in
the github action:<br>
<br>
<font face="monospace">### SETUP ###<br>
<br>
cd ~/esp/Open-Vehicle-Monitoring-System-3<br>
<br>
# setup branch:<br>
git remote add llange <a class="moz-txt-link-abbreviated
moz-txt-link-freetext"
href="mailto:git@github.com:llange/Open-Vehicle-Monitoring-System-3.git"
moz-do-not-send="true">git@github.com:llange/Open-Vehicle-Monitoring-System-3.git</a><br>
git branch -t experimental-esp-idf-build-workflow
llange/experimental-esp-idf-build-workflow<br>
<br>
# switch to branch:<br>
git checkout experimental-esp-idf-build-workflow<br>
git submodule update --init --recursive<br>
<br>
# apply mongoose patch:<br>
git apply
--directory=vehicle/OVMS.V3/components/mongoose/mongoose
vehicle/OVMS.V3/support/mongoose-espv5.patch<br>
<br>
# install v5 sdkconfig defaults:<br>
cp vehicle/OVMS.V3/support/sdkconfig.defaults.esp5
vehicle/OVMS.V3/sdkconfig.defaults<br>
<br>
# install v5 idf components:<br>
cp vehicle/OVMS.V3/support/idf_component.yml.esp5
vehicle/OVMS.V3/main/idf_component.yml<br>
<br>
<br>
### BUILD ###<br>
<br>
cd ~/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3<br>
<br>
# launch docker shell:<br>
docker run --rm -v $PWD:/project -w /project -it
espressif/idf:release-v5.0<br>
# init docker image (needs to be done on every start):<br>
apt-get update && apt-get install -y dos2unix<br>
<br>
# OPTION 1: start with default config:<br>
rm vehicle/OVMS.V3/sdkconfig<br>
# NOTE: this will build for ESP32 >= rev3, excluding the
SPIRAM bug workarounds<br>
<br>
# OPTION 2: update your existing sdkconfig:<br>
idf.py menuconfig<br>
# → press '/'<br>
# … enable FREERTOS_ENABLE_BACKWARD_COMPATIBILITY<br>
# … disable FREERTOS_ASSERT_ON_UNTESTED_FUNCTION<br>
# … disable MG_ENABLE_SSL<br>
<br>
# build:<br>
idf.py build<br>
<br>
# flash & start USB monitor:<br>
idf.py app-flash && idf.py monitor<br>
<br>
</font><br>
The build boots & works, issues you described excluded.<br>
<br>
An issue I didn't expect:<br>
<br>
<font face="monospace">I (0) cpu_start: Starting scheduler on APP
CPU.<br>
E (0) task_wdt: esp_task_wdt_add(747): TWDT was never
initialized<br>
…<br>
E (10) task_wdt: esp_task_wdt_add(747): TWDT was never
initialized<br>
<br>
…and then repeated 4x per second:<br>
E (3130) task_wdt: esp_task_wdt_reset(783): task not found</font><br>
<br>
I'll try to find the cause, as we cannot silent these ("early"
logging) they make using the shell challenging.<br>
<br>
But, besides that, it has Wifi & cellular connectivity, so
looks very promising -- nice work, Ludovic!<br>
<br>
Regards,<br>
Michael</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>