Skip to content
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

Support for ESP-IDF 4.4.0 #711

Closed
wants to merge 12 commits into from
Closed

Support for ESP-IDF 4.4.0 #711

wants to merge 12 commits into from

Conversation

FaBjE
Copy link

@FaBjE FaBjE commented Jan 27, 2022

Espressif has released a stable version of V4.4
https://github.com/espressif/esp-idf/releases/tag/v4.4

"Forked" from this pull-request: #693
I've rebased it onto the current develop and fix the latest toolchain references.
All credits for the work go to @X-Ryl669 and @jonathandreyer !

Can be tested using the following config:

[env]
platform = https://github.com/FaBjE/platform-espressif32.git#espidf-440 
framework = espidf
platform_packages =
  ; use upstream forked ESP-IDF to use V4.4 until official platformIO package is released
  framework-espidf@https://github.com/FaBjE/esp-idf#v4.4-platformio

It still needs a updated idf framework package reference to the PlatformIO repository.
https://registry.platformio.org/tools/platformio/framework-espidf/versions

@Jason2866
Copy link
Contributor

It seems espressif did not uploaded the S3 toolchains to the Platformio registry

@FaBjE
Copy link
Author

FaBjE commented Jan 27, 2022

It seems espressif did not uploaded the S3 toolchains to the Platformio registry

https://registry.platformio.org/tools/espressif/toolchain-xtensa-esp32s3/versions

They are listed here?

@Jason2866
Copy link
Contributor

Jason2866 commented Jan 27, 2022

okay than is something wrong with your PR. CI does fail regarding S3 toolchains
I did a build without the S3 and CI is successfull https://github.com/jason2866/platform-espressif32

@FaBjE
Copy link
Author

FaBjE commented Jan 27, 2022

I see no build-tools for an ESP32s3 listed. ESP32s2 has its own https://registry.platformio.org/tools/platformio/toolchain-xtensa32s2/versions

But I'm working on a ESP32C3 platform. which works fine using this PR.
I can't help you with the S3. I'm happy to include some other commits if you find the issue.

@Jason2866
Copy link
Contributor

Dont know the issue for S3. I do not need the S3... My build does work without the S3 for ESP32 and ESP32-C3 and all CI examples are compiling successfull. Since you added S3 it should work (imho) when you add to a PR. For me the reason not to open a PR, since i can not provide a fully working setup for all supported mcu

@FaBjE
Copy link
Author

FaBjE commented Jan 27, 2022

I never added or claimed to add the S3 processor. I simply combined some commits from the other pull request to support ESP-IDF V4.4 and rebased them onto the current develop.
This pull-request is only for that, nothing more.

@Jason2866
Copy link
Contributor

Jason2866 commented Jan 27, 2022

And it is not working. Somewhere is a bug. The CI examples have to compile.
The are ESP32 based.

@Jason2866
Copy link
Contributor

Jason2866 commented Jan 27, 2022

Added S3 and it does compile https://github.com/Jason2866/platform-espressif32/runs/4967725588?check_suite_focus=true
My branch https://github.com/tasmota/platform-espressif32/tree/IDF44/ESP32-S3
You are welcome to copy the parts which fixes your setup.
EDIT: Verified as working. Tasmota does start on the S3 (builded with this setup)

@brainstorm
Copy link

This seems like a slightly broken duplicate of issue #716?

@jonathandreyer
Copy link

Hi @FaBjE , Hi everyone,

For your information, I have updated the version for ESP-IDF v4.4.1. You can find more information here.

Best regards,

Jonathan Dreyer

@valeros valeros closed this in d4bfc01 Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants