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. |
|
@jeremiahrose As far as I understood is that there is a business disagreement between Espressif and PlatformIO. That's the sole reason why PioArduino was started. |
|
Thanks @TD-er for the context. TL;DRPlatformIO and Espressif are no longer friends, and PlatformIO is refusing to merge community PRs for new Espressif devices. Community development is now happening at https://github.com/pioarduino/platform-espressif32, and PRs can be submitted there to add new boards :) |
|
@jeremiahrose also, the way it works this is not only one repository but a complete set of repos which work together. Merging back will just transform platformio to pioarduino, so useless. They work differently and source their artifact at different locations. There are also several things that are added to pioarduino and works well like hybrid compilation which allows to add some esp-idf compile flag and exclude esp-idf modules through the platformio.ini file. |
While this thread focuses on technical aspects, we are in discussions with Espressif about the business value of the Arduino framework for their goals. Recently, Espressif shared that they don't see significant business value in the ESP32/Arduino solution. As a result, they have decided that Arduino IDE will remain the only official tool for starting with their products. The reason behind this approach is straightforward: they aim to guide users towards ESP-IDF. For silicon vendors, business priorities like revenue often outweigh the developer experience.
If the PlatformIO/Arduino community isn't a priority for Espressif, why should it be for PlatformIO Labs? Supporting Espressif's customers requires significant effort and investment from us. You might argue: "This could cost you some developers". However, our success isn't measured by the number of users; this is not a key performance indicator (KPI) for us. Our mission is to change how modern embedded systems are developed. Since 2014, we have introduced new ideas like declarative principles and test-driven development to the semiconductor industry. Initially, many silicon vendors ignored or dismissed us, but today these ideas have become industry standards. For example, Arm recently introduced support for multi-toolchains and dependencies in their CMSIS solution for VS Code - something we pioneered years ago.
Yes, we received an email from Espressif last week. They have decided to remove all mentions of PlatformIO from their website and documentation. Their stated reason is that "Arduino IDE is the only official tool for working with the ESP32/Arduino framework".
This development platform is still active. We continue to provide support for the ESP-IDF framework, which is widely used by businesses. In fact, the number of businesses depending on PlatformIO/ESP-IDF is growing every month.
We are closely monitoring the situation with multiple forks of this development platform. Unfortunately, the results so far have been negative. Contributors to these forks are aware of the challenges and are ready to deal with them, but many end users are confused. They don't realize these forks are unofficial and unrelated to Espressif or PlatformIO. As a result, we have been receiving complaints about instability and bug reports in our repositories, even though these issues originate from the forked platforms. For example, see platformio/platformio-core#5055 We kindly ask the authors of these forks to add a clear NOTICE/WARNING to their dev-platforms Wishing you a wonderful holiday season! 🎄🎉 |
|
Lol -- Both Arduino IDE and ESP-IDF is so abysmally horrible compared to PlatformIO + VS code + arduino, you'd think Espressif would want to keep the PlatformIO/Arduino thing going. As I'm working on products and have the future in mind, I must ask: Is platformio/platform-espressif32 being no longer developed from here on? or Is platformio/platform-espressif32 under continuing development and expected to continue into the future; but espressif/arduino-esp32 is not being continued by PlatformIO (so we would have to rely on other groups' versions of it)? |
|
@b314b do you work on commercial products? |
|
Its very sad to see that this will be the outcome of an previously awesome toolchain. Unfortunately i can't keep using outdated or arduino community stuff as they are not being supported by espidf. the only way forward seems to be using espidf directly, none of the attempts to run the pioarduino or other suggested methods have worked for me, every time i add something (like an component) i get an hell of undefined or broken stuff coming from apparently nowhere. |
|
Indeed, came to the same conclusion...
…On Mon, Dec 30, 2024, 6:33 p.m. Italo Soares ***@***.***> wrote:
Its very sad to see that this will be the outcome of an previously awesome
toolchain. Unfortunately i can't keep using outdated or arduino community
stuff as they are not being supported by espidf. the only way forward seems
to be using espidf directly, none of the attempts to run the pioarduino or
other suggested methods have worked for me, every time i add something
(like an component) i get an hell of undefined or broken stuff coming from
apparently nowhere.
—
Reply to this email directly, view it on GitHub
<#1225 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIRPKZP7DY6UHWYOEAUWVL2IHJ6HAVCNFSM6AAAAAA65MARK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGAYDONRZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
same here
From: Guil-T ***@***.***>
Date: Tuesday, 31 December 2024 at 11:08
To: platformio/platform-espressif32 ***@***.***>
Cc: mars000 ***@***.***>, Manual ***@***.***>
Subject: Re: [platformio/platform-espressif32] Support Arduino ESP32 v3.0 based on ESP-IDF v5.1 (Issue #1225)
Indeed, came to the same conclusion...
On Mon, Dec 30, 2024, 6:33 p.m. Italo Soares ***@***.***> wrote:
Its very sad to see that this will be the outcome of an previously awesome
toolchain. Unfortunately i can't keep using outdated or arduino community
stuff as they are not being supported by espidf. the only way forward seems
to be using espidf directly, none of the attempts to run the pioarduino or
other suggested methods have worked for me, every time i add something
(like an component) i get an hell of undefined or broken stuff coming from
apparently nowhere.
—
Reply to this email directly, view it on GitHub
<#1225 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIRPKZP7DY6UHWYOEAUWVL2IHJ6HAVCNFSM6AAAAAA65MARK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGAYDONRZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#1225 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEURLDYLUIYGRG2IXGUAGP32IHN6PAVCNFSM6AAAAAA65MARK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGAZDGMJTGM>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
@b314b but...IDF uses VSCODE as IDE. |
|
@0x0fe , do you mean this extension? Reading the latest reviews gives us a better understanding of why there is so much interest in the PlatformIO/ESP-IDF integration. Next year, we will focus more on this integration and work on adding new features. In the meantime, if anyone wants to get started with PlatformIO/ESP-IDF, we recommend checking out our PlatformIO/ESP-IDF Configuration Guide. Happy New Year! 🎄 |
|
Hehe. These reviews are hilarious. Idf extension is still a mess. With platformio or now with pioarduino I just install the extension and it works. |
|
So lets get this straight.
So this package is still being maintained but not for the Arduino framework. Correct? |
|
@FlavioZanoni I'd say that's a pretty solid summary of the situation, at least from my perspective 👍 |
|
|
@FlavioZanoni You missed one point: PlatformIO uses a business model where they charge the platform providers to be included and the PlatformIO users get it for free. So I'd assume that the PlatformIO wanted to have a little money chat with the Espressif folks who weren't interested in forking over money when they'd really prefer developers use the ESP-IDF they provide. |
PlatformIO always has had costs to operate its business, so I really can't imagine they were not being paid before by Espressif et.al. Having devs on the payrole and buying bandwidth does cost money. |
|
Because of this situation, I use Arduino more as a utility library rather than a framework, and for many things I already had to use ESP-IDF directly. |
@genemars : PlatformIO is tooling, you usually do not chose a framework or development base depending on a tooling, which is more about user preference. I.e. you could go CLI, with 3 different vscode extensions (pioarduino, plaformio, esp-idf), Arduino IDE, etc Each having pros and cons. PlatformIO as it is right now is a valid option for esp8266, esp32 arduino 2, esp-idf, and other platforms. They just stopped supporting Arduino platform but their tooling also supports other languages and platforms. Tooling should not be the main driver decision for your project ;-) |
As mentioned by several people before, you can try pioarduino. |
|
From my side I can tell only one thing. It remains to be proven whether pioarduino will be the free answer to PlatformIO on esp32. I have a lot of confidence in the pioarduino team, but it is clear that, being a project without a solid business model, it is more susceptible to the wind than PlatformIO has been. I sincerely can't wait to find another reason to abandon Espressif. |
@TD-er, I already did and my project also works with pioarduino, but I'd prefer to stay on an official solution and I don't know if the pioarduino project is going to be active in the long term. @mathieucarbou, I know it's just tooling but this is the first thing you choose when you start a project. And after lot of research (back in 2019) I choosed platformio because of the existsing codebase and examples I could reuse from |
The part of breaking changes I do understand as that's something that is unavoidable if you want to move forward. I'm not sure if for pioarduino a financial businessmodel is required. If it were only a single person maintaining an important tool you depend on, then I would also have my doubts. |
@sblantipodi, Espressif SoCs are the most versatile, cheap and powerful solution out there. All ESP products have been amazing since the very beginning. I don't see a reason to back out. |
|
Actually I find it somewhat confusing that espressif seems to be quite proud of the high number of esp-based projects on github,
I guess that more than half of these "115K+" have a |
PlatformIO is a tooling, not a platform. To use PlatformIO tooling, someone needs to develop the glue (integration) between the framework (arduino core, esp-idf, etc) and the tooling (vscode extension, CLI, etc). So what has been stopped since Arduino Core 3 is that PlatformIO does not take care of this "glue" anymore. But pioarduino does, with the help of Espressif Arduino Core devs. Making a parallel with other languages, Nebeans and JetBrains are not paid by Oracle or Azure to add support for Java in their IDE. Pyhon does not pay vscode or others to have support for their languages in vscode or other IDE. Maven and Gradle tooling for Java projects are not paid by the different things they integrate to support them. So this is normal that Espressif does not pay any third party to add support for their platform. What Espressif can do though, but not obligatad to, is help building (or, even more build) the glue between existing tooling and their stuff, existing tooling being PlatformIO, IDEs, etc. But most of this stuff, in other languages ecosystem, comes from the community, like pioarduino. The more people get involved with and in pioarduino, the more it has chances to survive and be resilient. |
esphome is using pioarduino since a while now too. There are enough skilled developers in background of pioarduino to keep it alive as long espressif MCUs are widely used. |
You'll "abandon" espressif SoCs because a third party package manager drops the support of arduino core, alright, sounds perfectly reasonable.
guess != facts, not sure how one can assume these projects are only possible thanks to PIO. It is just a package manager, the editor is microsoft VSCode, the toolchain is Espressif IDF. the majority of commercial projects are not using pio but just the official IDF with eclipse IDE, or IDF with VScode or even arduino with its IDE. I wonder how all these peoples so disturbed and concerned about a third party package manager dropping support of Arduino, another third party SDK, can work on actual commercial projects with exotic SoCs or MCU where there is only one possible IDE (often Eclipse based) and toolchain, no "libraries", no chatgpt, or when you can only work on keil UV5 (no syntax highlight, no code browse etc). Come on guys, its just a package manager, there are plenty of options to not use it and still work on IDF, and even vscode, even if you want to use Arduino core, and contrary to what has been said the official VScode extension works perfectly well, there is like 700 closed tickets and 20 open, and if you have a problem you just need to reach out to Espressif by email or with your allocated FAE. If PIO has so much value, they can sell it and peoples will buy, i guess ;) I think the lesson to be learned here is to not thrust third parties that pretend to be "open source" and "community", because as you can see, if there is no money to make, then the "community" part will vanish very fast, lol. |
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: