This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
Implement ESP32 support #156
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
…t enough code you can build for any platform...
…ent state needed to be expected/handled.
… fail during testing
Closed
…essions, basically just pass thru to synchronous configTzTime. The Async logic isn't used for ESP32
|
Awesome starting point, thanks for your effort! I will merge it into the branch, and hopefully will have some time coming weekend to have a better look and see where I can help. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Here are the steps I use to compile and deploy the /HelloWorld example to an ESP32 device.
Many, but not all, of the framework's features are implemented. Search for "Implement ESP32 version" to understand exactly which sub-features are pending. In short, currently for ESP32 builds:
Personally not used these features in my projects, so haven't invested time porting them.
Note: Startup will block for 60secs for fresh device without SSID name/password configured. The 60secs is for some existing connect timeout code. Look at monitor output traces to observe this. Eventually captive portal will start. imo, cause is behavior/bug in the existing WifiManager.cpp startup logic. Hopefully startup time to be improved in the esp8266-iot-framework orthogonal to the ESP32 focused edits in this pull request.