Update TLS client example for Espressif ESP8266 #7240
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gojimmypi
force-pushed
the
PR-wolfssl_client_ESP8266
branch
from
5f6d0ed
to
68fb183
Compare
dgarske
approved these changes
Feb 13, 2024
|
@lealem47 is going to test it with a customer. |
|
Customer confirmed it's working. |
lealem47
approved these changes
Mar 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Adds wolfSSL TLS client example
makeandcmakesupport for the Espressif ESP8266.This update is in addition to the various ESP32 flavors, although the ESP32 only supports cmake build with the ESP-IDF.
Adds a VisualGDB project file, located in project root, not VisualGDB subdirectory.
Fixes the
NO_SHAissue mentioned in #7210Introduces
WOLFSSL_ESPIDF_BLANKLINE_MESSAGas the ESP8266 SDK does not allow a blank string foresp_log().Various other cleanup & polish.
Note regarding VisualGDB files: my plan is to keep only 1 basic ESP32 and 1 ESP8266 project file in each example directory except for the template project. For the template example directory, I plan to have all the various flavors of ESP32 SoC chipsets with a note that that files can be copied as-is to other project directories as desired.
The VisualGDB paths are all relative in the project file and it seems they can be copied to any Espressif project.
Fixes zd# 17001
Testing
How did you test?
Tested with
make("make build") &cmake("idf.py build") on command line, as well as using VisualGDB.Hardware tested with Adafruit Feather HUZZAH as well as a generic ESP8266 dev board.
Checklist