Esp8266/ESP32 reset handshake for the serial connection#432
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In certain circumstance ESP device could be left in unspecified state. This PR add following new option:
that allows:
reset the ESP32/Esp8266 board at the beginning
after the reset is performed, we read the initial HyperSerialEsp8266/HyperSerialESP32 boot message and check it
if the board is not capable of the 2Mb speed (or any other speed set in HyperHDR) the user will see a warning
after the LED device is stopped, we read the statistics (just wait few seconds). Still we maintain one way communication at the same time, because of problems with the performance of duplex for certain system/drivers.
Also please check out other new feature added in the previous commit, that shows how many frames were dropped due to slow LED device or too high refresh rate set in the smoothing: