-
Notifications
You must be signed in to change notification settings - Fork 831
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
srp errors -> 5.6.6-stable-update2-esp32 #7155
Comments
@gojimmypi I have installed Check my git here: https://github.com/AchimPieters/esp32-homekit-demo also for my current user_settings.h Can find the WOLFCRYPT_HAVE_SRP and WOLFSSL_BASE64_ENCODE in user_settings.h ? As described in #6870 (comment)
|
Hello @AchimPieters -
That sounds like the version from the wolfSSL Managed Component, which likely has a different You'll need to convert it to a non-managed component and copy in your prior, working Cheers |
@gojimmypi followed all instructions as described in srp errors #6870, but now I got new errors?
For latest changes, see: https://github.com/AchimPieters/esp32-homekit-demo |
@gojimmypi I was thinking about closing this one and opening a new issue because it became another error, what do you think? @dgarske your insight was the solution last time, maybe you could help also this time? |
moved to : esp32_sha errors -> 5.6.6-stable-update2-esp32 #7210 |
Great news! The latest code works with all the ESP32 flavors! Please confirm you are using files from the 5.6.6 release (or later).
The examples now contain an updated components/wolfssl directory, in particular a user_settings.h that has a section to detect which ESP32 flavor was selected with the
idf.py set-target
command. (e.g.CONFIG_IDF_TARGET_ESP32C6
, etc)Hardware acceleration is enabled for all the SoC's supported by ESP-IDF v5.1. Newer chips will work, with HW disabled for any of those undetected.
Note there was a post release change in #7148 that fixed the environment variable option to point to your wolfssl source, if not in the same
[workspace]/github clone
structure.If you cannot get it working, please open a new issue so we can track it with visibility. Thanks!
Best Regards.
Originally posted by @gojimmypi in #6870 (comment)
The text was updated successfully, but these errors were encountered: