<html><head>
</head>
<body><div>Hi Ludovic</div><div><br></div><div>Thank you for all your efforts to get ESP-IDF to the newest version.</div><div><br></div><div>The reason why I have not been able to test along the way is, that I was not able to set up a native, non-docker, working test environment with the newer ESP-IDF versions.</div><div><br></div><div>Is there a "step by step" documentation for setting up these newer versions without docker? That would be really helpfull.</div><div><br></div><div>Regards</div><div><br></div><div>Chris</div><div><br></div><div><br></div><div>Am Donnerstag, dem 18.05.2023 um 00:05 +0200 schrieb Ludovic LANGE:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><p>Hi List,</p><p>If possible, I'd like a peer-review / discussion of the following PRs:</p><div> </div><ul> <li><a moz-do-not-send="true" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/901">ESP-IDF v4+: we do not have uxMutexesHeld any more #901</a><br> <br><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><div class="edit-comment-hide"><div class="comment-body markdown-body js-comment-body
soft-wrap css-overflow-wrap-anywhere user-select-contain
d-block"><p dir="auto">In ESP-IDF 3.3.x builds of OVMS, we're using a fork of ESP-IDF. In this fork, FreeRTOS has been patched with <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/openvehicles/esp-idf/commit/95e43fc2c4360f8126a0985bf037a293bebe3767/hovercard" href="https://github.com/openvehicles/esp-idf/commit/95e43fc2c4360f8126a0985bf037a293bebe3767">openvehicles/esp-idf@<tt>95e43fc</tt></a> to add a <code class="notranslate">uxMutexesHeld</code> field in <code class="notranslate">TaskStatus_t</code>.</p><p dir="auto">However, in the ESP-IDF >= 4 build we're using mainstream ESP-IDF (for the moment), which does not include this field.</p><p dir="auto">So we adapt the display to handle both cases.</p></div></div></div></blockquote> <br></li> <li><a moz-do-not-send="true" href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/902">ESP-IDF4+ : crash handler and boot status #902</a><br> <br><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><div class="edit-comment-hide"><div class="comment-body markdown-body js-comment-body
soft-wrap css-overflow-wrap-anywhere user-select-contain
d-block"> <ul dir="auto"> <li>error handling rework (<code class="notranslate">xt_set_error_handler_callback</code> is only available in our ESP-IDF 3.3.4 fork.)</li> <li><code class="notranslate">esp_task_wdt_get_trigger_tasknames()</code> not available (<strong>feature removed</strong> from ESP-IDF4+ builds) TODO</li> <li>first steps to support other archs than XTensa in <code class="notranslate">boot_data.crash_data</code></li></ul></div></div></div></blockquote> <br></li></ul><p>These are the <b>last 2 PRs</b> before being able to build with any of these ESP-IDF versions : 3.3.4-ovms, 4.4.4, 5.0, 5.0.1, branch-v5.0, branch-v5.1, latest - the last mile !</p><p>(One <a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/903">workaround PR</a> is pending to be able to <b>run</b> one of these new versions, preventing a crash at boot - but it needs a proper analysis first)<br></p><p><br></p><p></p><p>Also, with these 2 PRs, we will be able to enable automatic builds on all these versions on master (using GitHub "Actions") - you can have a preview of what I mean here : <a class="moz-txt-link-freetext" href="https://github.com/llange/Open-Vehicle-Monitoring-System-3/actions">https://github.com/llange/Open-Vehicle-Monitoring-System-3/actions</a></p><p>As we're slowly entering a period of transition between ESP-IDF 3.3.4-ovms and a more recent one (5.0.1 ?), we will need a way to ensure that the PRs / commits are OK across all these versions. Automatic builds can be configured to build on all targeted ESP-IDF versions, and can report their result back in the PRs, so that we can trap potential compilation errors before merging.<br> (Especially as in the newer ESP-IDF versions, more and more warnings are treated as compilation errors)</p><p>I also prepared a check for documentation errors using the same mechanism.</p><p><br></p><div> Thanks in advance. </div><p>Regards,<br></p><div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div><div>_______________________________________________<br></div><div>OvmsDev mailing list<br></div><div><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br></div><div><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br></div></blockquote><div><br></div><div><span></span></div></body></html>