Support Arduino ESP32 v3.0 based on ESP-IDF v5.1 #1225
Comments
|
I've been trying this with following config: ; see https://docs.espressif.com/projects/arduino-esp32/en/latest/installing.html#how-to-update-to-the-latest-code
[env:arduino-latest]
platform = https://github.com/platformio/platform-espressif32.git
board = az-delivery-devkit-v4
framework = arduino
platform_packages =
framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32#masterbut the build fails with |
|
See the updated comment #1225 (comment) |
|
Adding Arduino 3.0.0 support is the only way to make the ESP32-C6 available for Arduino projects. |
@ivankravets Does this mean that Espressif has dropped any support? Looking in current Arduino 3.0.0 code (branch master) everything regarding Platformio support is there. |
|
Hello all, I do work in Arduino Core ESP32 project as a Project Manager so I would like to clarify this from our Team point of view. Please take a look on this comment in original Pull request. We also update a warning note in our documentation which should be a bit confusing. To not duplicate what is written in original PR, we will be glad if PlatformIO supports our latest version and we are open to any contributions. @ivankravets Feel free to contact us any time directly, we will be happy to discuss this if you see any points we can do differently. Thanks |
@Jason2866 |
|
@ivankravets I think a reason why many users use PIO is also to keep some of the arduinoesp32 APIs while having the possibility to modify the IDF SDK configuration (menuconfig) which is necessary in many cases and not possible in arduino, unless using the libbuilder (buggy and not convenient). Maybe it would be wise for PIO to directly use arduinoesp32 core as is, and just focus on allowing users to run arduinoesp32 core along with IDF to keep access to menuconfig. |
|
I am concerned about the viability of this repo long-term as folks like @Jason2866 have started to roll their own and this repo not catching up I am currently using his https://github.com/tasmota/platform-espressif32/tree/Arduino/IDF5 branch and it works mostly great for me - even if I feel uneasy about relying on a private effort with unclear future - how do you see the longer-term perspective of your fork? This fork has diverged from this repo massively - not sure this can brought back here easily the other issue I have is the abysmal debugging experience esp32/pio/arduino compared to using straight IDF |
|
@mhaberler i did the same yesterday and used https://github.com/tasmota/platform-espressif32/tree/Arduino/IDF5 But then when building it complained of missing SPIFFS, i added it manually from previous version (in components directory) but then i get a dependancy error with esp_partition.h, despite it is well present in "components". Did you met this issue too? |
|
@0x0fe @mhaberler My fork has not the goal to be compatible to anything official. Since project Tasmota is always in first row for new stuff, and is active in contributing to espressif Arduino Core, there was the need to have the development version of Arduino Core available with Platformio. The needed changes for Arduino 3.0 in Platformio are not many. A small job for @valeros |
|
@Jason2866 oh, i see, that explains the error with SPIFFS |
|
alpha stage - fair enough. Now assume Core 3.0.0 gets released - does this have any bearing on the debugging situation? who has the ticket to make that work? I'm talking about openocd + gdb versions and matching debug configs which work - at least somewhat like Nordic Connect and Segger I admit I am slightly confused about players and the who-does-what-and-why-not - I might be barking up the wrong tree (or repo) for that matter |
|
@mhaberler Does debugging work in espressif IDF env setup? If yes imho Platformio has the job for the devices which are currently supported with IDF 5.1. Not saying it will be easy to solve or it will be done soon. The debug issue for the C6 is known and there is an open issue. |
@0x0fe yes, same here `Failed to resolve component 'spiffs' |
you mean like command line/shell? yes, repeatably |
|
@mhaberler It makes sense, well SPIFFS yo ucan add it manually from previous version but then you will get an error with esp_partition, and i am not sure where to re-enable the SPIFFS module and dependencies correctly. |
https://github.com/platformio/platform-espressif32 isn't a core itself. It's a software piece that makes the PlatformIO Build API work seamlessly with Espressif 32 products within the PlatformIO ecosystem. If you check the source code of this repository, you'll find other integrations, like ESP-IDF. If we support Zephyr/ESP32, it'll also be found here.
We do use it directly (https://registry.platformio.org/tools/platformio/framework-arduinoespressif32). There's no common ground between Arduino IDE and PlatformIO. The "arduino" in PlatformIO is just a framework. PlatformIO supports over 10+ different frameworks. The reason many developers see PlatformIO as a "replacement for Arduino IDE" is due to source code compatibility and advanced project management with lots of configuration and collaboration features based on PlatformIO's unique declarative principles. If you've tried another framework besides "arduino", you'd notice there's no difference in the configuration aspect. You and your team can focus on project development without wrestling with bootstrapping and collaboration issues. Lastly, for a VSCode-based solution with native ESP32/Arduino core support, I recommend the Arduino IDE for VSCode extension backed by Microsoft. It's similar to Arduino IDE 2.0 but uses VSCode as the editor. Both leverage "arduino-cli", so the build system and workflows are the same. |
|
@ivankravets I see, glue logic layer. the totally different versioning between these platforms and the cores they implement is rather annoying, though. |
|
@ivankravets make me understand what your recommendation means - are you saying: When I prefer to use VSCode, I should take the Microsoft Arduino extension for VSCode and drop Platformio? |
|
@mhaberler, we value openness in our community and aim to give you the freedom to choose. If there's a newer version of the software not yet supported by PlatformIO, we won't hide it. The current supported version is Arduino Core v2.x for ESP32. Our collaboration with Espressif, including discussions about renewal, is ongoing. It's worth noting that we have @VojtechBartoska, a project manager from Espressif, in this thread. We're all working together to ensure you receive the best features and support. We'll keep everyone posted on any updates to ensure a smooth continuation of our services. |
|
I can see there's a bit of political project stuff happening, but as an end-user, all I want to do is be able to use the latest Arduino framework. Consider this a vote of support for making that happen, however it needs to be. |
|
PlatformIO is a commercial open-source project. In the past, it used to be a paid service before 2020, following a business-to-consumer (B2C) model. Unexpectedly, PlatformIO gained widespread popularity among millions of developers globally. Consequently, we shifted our strategy to make powerful tools for professional embedded development freely accessible to everyone. The active development and maintenance of PlatformIO, along with its infrastructure, are now supported by technology partners dedicated to delivering an excellent developer experience. Espressif was one such partner, and we appreciate their long-standing collaboration. Currently, Espressif has ceased support for new products in PlatformIO, but rest assured, we are committed to providing support for existing Espressif products integrated before this change, as per our technology licensing policy. Your projects won't face disruptions, and services will continue as usual. If there's significant interest from Espressif customers in PlatformIO, we'll reach out to Espressif and explore the possibility of continuing our collaboration. If you have any questions or need clarification, feel free to ask. We're here to provide all the answers you need. |
|
ok, so Espressif jumped ship @ivankravets what does that mean for the subject topic - Arduino3? your wording would suggest to me "no new Espressif releases - be it Arduino or ESP-IDF, existing releases go on life support" are you saying this repo stops at ESP-IDF 5.1.1/Arduino2 until Espressif changes its mind ? |
|
@mhaberler Looks like: as long there is not enough feedback from Platformio users wanting actual espressif framework support, there is no good position from Platformio side to argument why espressif should invest money having Platformio support. |
|
As an implementer rather than a coder, I just like to get things done. PlatformIO with arduinoespressif32 framework enables me to do just that. I use PlatformIO for other types of projects/coding and it helps me a great deal to have the IDE consistency and also the great editing/support features of the platform. Because I am not a C coder, I find everything about how these things work together extremely confusing. I have spent days trying to work out whether ESP32-C6 could be supported or not. I decided to try the last few comments above (from @Jason2866 and @empewoow) and was thrilled this morning to get my standard MQTT client code to compile and run on an ESP32-C6, along with voltage measurement. To get this to work, I have used a combination of adding a section to platform.ini: Some of these lines come from https://github.com/letscontrolit/ESPEasy/blob/mega/platformio_core_defs.ini as advised elsewhere. I'm not sure if they are all necessary. I also added a file: /boards/esp32-c6-devkitc-1.json as per @Jason2866's #1225 (comment) (above, a few comments up). A huge thank you to all, both paid and unpaid, for putting so much effort into these projects. I wish it was simpler to understand the versions and how they interact, but the fact that they are there in the first place is an amazing feat of human endeavour. I hope to try some ZigBee code next and get an endpoint up and running. Now that would be something. |
|
Hi @ivankravets . I'm wondering if you have had a chance to review my pull request to add Arduino ESP32 v3.0 support to PlatformIO. #1281 Thanks (Note: This is not about Espressif supporting PlatformIO, but updating PlatformIO to support Espressif ESP32 v3.0, which was a relatively small change that I am happy to contribute to PlatformIO). |
|
Well. I, and my team are very confused hearing this. What is espressif thinking? As others said, the Arduino IDE is a toy. We need a much more robust IDE. Our project grow so much in the past year using PIO with arduino,idf, we can't go back to only arduino or only idf. Maybe its time to find an other chip... :( Really sucks to stuck on idf 4.4.0 and arduino 2.0.0... |
|
Obviously espressif are thinking their VSCode plugin is a replacement for Platformio, which basically means developers are now in the business of helping develop and debug their plugin rather than their own code. The chaps working on it are nice and try the best, but the results are beyond pale. If you think this is too harsh a critique, have a read of its reviews Frankly the IDE situation for espressif users is preposterous. And I have no idea why other companies being perfectly capably of coming up with a competitive product are letting espressif get away with this quality of developer support. |
|
We will know soon what happens. Platformio never supported not released versions. |
|
Well, if we can easily port our code to vscode idf from pio arduino,idf i see it as a win to use the latest. PIO was always behind on versions. |
|
I haven't understood one thing, is platofrmio going to support Arduino core 3 or not? |
|
Trying this config: But got this error: _* [.pio\build\esp32-s3-devkitc-1-n16r8v\bootloader.bin] Source |
|
Pin the platform! the memory mode is not valid. This should work The error you see is from a wrong setup for the board. PSRAM fixes are not needed for S3/S2. |
|
Better use this boards.json |
|
@Jason2866 thanks for your reply, it solved my problem described above. main.ino #include <TFT_eSPI.h> // Hardware-specific library
#include <SPI.h>
TFT_eSPI tft = TFT_eSPI(); // Invoke custom library
void setup(void) {
tft.begin(); <---- CAUSE OF ERROR
}
void loop() {
}Expected result: App successfully launched platformio.ini Assets: |
|
Off topic. There is no software programming support. Just can say we are using our Platformio fork to compile project Tasmota and it does work as expected. |
Strange, i got these errors |
|
Platformio seems screwed up. Close VSC and delete the hidden folder |
|
I've got a |
I have deleted .pio folder, restarted vscode and i got the same error :/ |
|
This is my PIO.ini |
|
You changed the setup too |
|
Oh, i see.... :( |
|
Thank you for the clarification |
|
Looking through this long thread, I haven't catched one important thing and I'm not alone with that - @sblantipodi also didn't catch that. |
|
Espressif does not support PIO. They stopped. PIO said they want to support us but if Espressif does not give them money for it, they wont. So they will wait for enough user feedback to go to Espressif for support. Until this resolves, we are ( as users of PIO ) not supported. |
|
I don't know if this is the best way to proceed: I'm not an expert and I have nothing to teach to Ivan but sharing some data from the PlatformIO registry that shows how many users uses PlatformIO could be a better indicator for Espressif than some comments on an issue like this. I really hope that things will move forward on this topic, this "uncertainty" is not good for the PlatformIO project and for all the people that uses it. |
and others
The ESP32 Core for Arduino 2.x is the most recent major version currently recommended for use with PlatformIO. The decision to discontinue support was made by the Espressif company, as indicated in their official statement: espressif/arduino-esp32#8606
If you're an Espressif user who relies on PlatformIO for your projects, kindly share your thoughts in the comments below and cast your vote on this matter. Once we gather enough interest from the Espressif community, we plan to reach out to the Espressif company and request a reconsideration of support for PlatformIO.
The text was updated successfully, but these errors were encountered: