Skip to content
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

start_wifi(): ESP32 did not respond with a startup message #10

Closed
dhalbert opened this issue May 23, 2024 · 0 comments · Fixed by #11
Closed

start_wifi(): ESP32 did not respond with a startup message #10

dhalbert opened this issue May 23, 2024 · 0 comments · Fixed by #11

Comments

@dhalbert
Copy link
Contributor

ESP32.reset() wrongly assumes that the ._uart exists when it checks for a startup message. But that's only true if you did .start_bluetooth(). If you just do .start_wifi(), ._uart won't be created and the check for the startup message will fail.

So .reset() should not check for a startup message if ._uart is None. You might wonder whether the code should always create a UART, but there are AirLift boards where the UART pins are not connected by default: you have to solder some jumpers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant