-
Notifications
You must be signed in to change notification settings - Fork 107
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
esp-idf 5.3.2 fails on P4 #1387
Comments
Indeed, a little surprised this didn't show up sooner, they must have added extra checks under the hood in this release. Using the SOC capabilities is definitely the way to go. Not repeated to this issue, but there are other places in the code that we previously had to use the esp32 chip definition to decide to enable features, but these should all be replaced by the SOC capabilities definitions, now that that is supported in all current IDF versions. |
Fixes atomvm#1387 Signed-off-by: Peter M <[email protected]>
Fixes atomvm#1387 Signed-off-by: Peter M <[email protected]>
Fixes atomvm#1387 Signed-off-by: Peter M <[email protected]>
Fix esp-idf >= 5.3.2 P4 builds 5.3.2 needs extra guards for esp32-P4 espressif/esp-idf@706935f Fixes #1387 These changes are made under both the "Apache 2.0" and the "GNU Lesser General Public License 2.1 or later" license terms (dual license). SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later
https://github.com/petermm/AtomVM/actions/runs/12200112028/job/34037206464
seems to be due to: espressif/esp-idf@706935f and we need to add
SOC_GPIO_SUPPORT_HOLD_IO_IN_DSLP
to the function guards.The text was updated successfully, but these errors were encountered: