-
-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to ESP-IDF v5.2.2 #1398
Comments
See https://github.com/platformio/platform-espressif32/releases and note the "Supported Frameworks" section |
apparently I can just override the entire /components and /tools folders with no problem (so far). |
As Valeros has already added this to the platformio repository, you can use the new SDK in the actual platform-espressif32 (until the new one is released) by the following in platformio.ini [env]
platform = espressif32@6.7.0 ; Includes ESP-IDF v5.2.1
platform_packages = framework-espidf @ ~3.50202 ; Forces to use ESP-IDF v5.2.2 compiled by Platformio Group.
framework = espidf
|
Is it possible to use a I've tried doing something like this:
but see errors like this:
I can otherwise successfully compile with PlatformIO releases:
Am I using the |
@gojimmypi It is not possible to use the espressif IDF repo as source nor a file or directory |
@Jason2866 thanks for saving me the additional effort of trying to get that to work! As noted in #1418 I'd like to use some changes I'm making to the ESP-IDF in PlatformIO. Are there any alternatives for me to do this, other than a brute-force method of copying files to my |
@gojimmypi Fork the IDF version you want to use. Do your changes. Add a valid package.json and version.txt in the root. Create a release. The github function release will NOT work since it does not include the git submodules. The generated release can be used with EDIT: Could you ping me if your wolfssl implementation is ready to use? I don't like mbedtls at all. Would like to try wolfssl :-) |
@Jason2866 that sounds like an excellent plan! Thank you so much. I'll give that a try! :)
I hear ya on the mbedTLS topic. It's clearly not a priority for them, but it is for wolfSSL. I have a copy of the Espressif HTTP/S example here with the ESP-IDF updates on my wolfssl branch. It basically works, minus the "certificate bundle" feature that is specific the mbedTLS at this time. See also: https://www.wolfssl.com/forums/post7724.html I do plan on resolving the certificate bundle topic, but for now I believe wolfSSL is otherwise working on my ESP-IDF fork with the There are more wolfSSL examples here (not using the
Absolutely! Do you have a specific project in mind? Note that wolfSSL simply for the PlatformIO environment should be working just fine: https://www.wolfssl.com/wolfssl-now-supported-on-platformio/ The issue I am working on is for those that really want to use the If you'd like to take this for a test drive, let me know. I'd love to have your input. Feel free to reach out to support@wolfssl.com as well. Cheers |
As title say, an update to ESP-IDF v5.2.2 or at least having an option to use ESP-IDF v5.2.2 would be great.
I'm trying to implement WiFI FTM localization and the FTM report API only exist in v5.2.2.
Or is there a way to force PlatformIO to use v5.2.2?
Also, There isn't really a documentation on the PlatformIO registry as to what ESP-IDF version does each framework-espidf version corresponds to.
Being able to easily see what ESP-IDF version each framework-espidf correspond to would be amazing.
Otherwise I'd have to migrate to ESP-IDF (which I really don't want to. I'm spoiled by PlatformIO at this point).
Thanks!
The text was updated successfully, but these errors were encountered: