Apply various Espressif compatibility updates #8066
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updates wolfCrypt for various Espressif device and environment / version compatibility.
A non-obvious but critical update is the
WOLFSSL_CMAKE_REQUIRED_ESP_TLS
detection in the new esp-tls component and bundle support. When a compatible environment is found, theesp-tls
component's respective<esp_tls.h>
is included so that the non-wolfSSLesp_tls_free_global_ca_store();
can be called during cleanup.As wolfSSL support is defined in the respective ESP-IDF
CMakeLists.txt
, theWOLFSSL_CMAKE_REQUIRED_ESP_TLS
is expected to be defined in that cmake file when the component support is added to the ESP-IDF.See my esp_http_client_example for an example.
Also, during testing on multiple different flavors of the ESP32 / ESP8266, some attributes in the memory library are not available and are now gated out.
Includes various spelling corrections, comment updates, and more.
Fixes zd# n/a
Testing
Tested on my 9-device jig, Espressif only
Checklist