So, as I understand it right now, we have some old IDF for the basic ESP32 build as we did before, and now we have 4.4.8 for the C3 and S3?
I'm all for attempting to move the original ESP32 build over to 4.4.8 too
However I have very limited time right now, and the choice to allow the _C3 build with IDF4 while keeping the standard ESP32C3 as before was done because I didn't have time to test ESP32 and ensure that swapping over to IDF4 didn't break something (because it probably will!).
We still seem to be in a position where I think the C3 build isn't connecting over WiFi, so ideally before we start messing around and breaking things even more, I'd ideally like to be in a state where everything's kind of working ok.
I feel like once we have that, building a sdkconfig.esp32c3/etc by diffing what we have with the default file should be pretty straightforward if we then want to go that route.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
So, as I understand it right now, we have some old IDF for the basic ESP32 build as we did before, and now we have 4.4.8 for the C3 and S3?
I'm all for attempting to move the original ESP32 build over to 4.4.8 too
However I have very limited time right now, and the choice to allow the _C3 build with IDF4 while keeping the standard ESP32C3 as before was done because I didn't have time to test ESP32 and ensure that swapping over to IDF4 didn't break something (because it probably will!).
We still seem to be in a position where I think the C3 build isn't connecting over WiFi, so ideally before we start messing around and breaking things even more, I'd ideally like to be in a state where everything's kind of working ok.
I feel like once we have that, building a sdkconfig.esp32c3/etc by diffing what we have with the default file should be pretty straightforward if we then want to go that route.