Looking for some help getting a project migrated from esp32 to esp32 solo. The only difference (of which I’m aware) is running in single core per the menuconfig utility. But, I’m using the ardunio framework. Setting the build flags in platform.ini still produced a dual core binary. I get this error after loading the binary,
E (459) cpu_start: Running on single core chip, but application is built with dual core support.
E (459) cpu_start: Please enable CONFIG_FREERTOS_UNICORE option in menuconfig.
Thank you for your response. The libraries from libernstone are binary. Is the ardunio framework in platformio built from, GitHub - espressif/arduino-esp32: Arduino core for the ESP32?
So, If I pull the espressif code, edit the configsdk (via menuconfig), and build in the ardunio ide, would I end up with an updated platformio framework? So instead of replacing four libraries and one header, I would be able to rebuild the arduino esp32 framework with any other config changes I might need to make? Is there a description of how to do that somewhere?
Once you have updated binaries for the latest version you can also integrate them in PlatformIO by using the platform_packages (docs) directive. For that just fork GitHub - espressif/arduino-esp32: Arduino core for the ESP32, push your new library / headers in there and use your new git repository to replace the framework-arduinoespressif32 package.
Due to that complexity I would however first suggest to try the last suppoert version from lbernstone, as seen above.
Just to close this thread. With help from @maxgerhardt and the libernstone library, I have my project building for esp solo chips. I still need to figure out how to rebuild the arduino framework. But for now, I’m moving forward again. Thank you!
You have to rebuild the arduino libraries with the correct menuconfig setting for running on a single core ESP. There are posts here to help with links to already-built libraries that work. If you end up rebuilding the arduino libraries, you also must copy the correct files into the correct platformio folders and you must use the correct version of the esp idf and correct version of the arduino source (there are posts here for that too). PlatformIO keeps track of all your installed build tools, so it can be complicated to setup an integrated workflow that also builds/reinstalls the arduino libs. I ended up using only the ESP IDF for my project and now have an integrated workflow for build/deploy/test.
Thank you for your quick response. It is wonderful that Max has put a lot of links here to help us. Now I understand all the work required to make it work for a new part.
I am able to use ESP IDF to build and flash the ESP32 Solo 1. I think I have the basic understanding to try it. I also can understand the approach you took. It is a great opportunity for me to learn how things work behind the PIO project.