Additional instructions:
When first building, your sdkconfig will be converted as some config options did change betwen ESP-IDF v3.x and v5.x.
Run `menuconfig` and :
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.
I may try this on my spare board as a start! (The Aux 12v switch didn't work... But otherwise it's mostly OK)
Michael.
On Thu, 26 Jan 2023, 4:41 pm Mark Webb-Johnson, <mark@webb-johnson.net> wrote:
Progress looks good on this. Thanks for stepping up to try to tackle it.
Pain points for me with our current approach are:
- RAM usage (in particular IRAM)
- IDF bugs that may be improved in newer versions
- Support for newer hardware (including ESP32-S3)
#3 would give us a welcome 12 more GPIOs with minimal hardware changes, but possibly worse RAM situation (520KB->512KB, see #1).
My preference would be v5 IDF (for the newer hardware support).
I think it would be fine to have this as a new branch. Not particularly important to make it work in the master one.
Regards, Mark.
On 26 Jan 2023, at 8:56 AM, Ludovic LANGE <ll-ovmsdev@lange.nom.fr> wrote:
Hi,
A quick note to share with you the progress on the ESP-IDFv4 + cmake endeavour:
- The branch https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v4-rework-network is now ready for greater review. Most of the warnings are gone, and I'll need some help for the last ones.
- I created a draft PR https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/806 . Not that I want to merge it as-is nor soon, but it may help the review process to have some central discussion point.
- I'll now switch to ESP-IDFv5 porting - on a new branch (based on the v4) : https://github.com/llange/Open-Vehicle-Monitoring-System-3/tree/experimental-esp-idf-v5 (empty at the moment).
Regards,