-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Reboot Stuck after ESPhttpUpdate #1782
Comments
Have you done physical reset after serial programming and before OTA update? |
@igrr, hmmm. Here's what I just did and it seemed to work:
Console Ouput
I guess it would work if I didn't have to serial program it first. Not sure what's happening there. |
This is a pretty old issue which isn't resolved yet: #1017. |
@igrr, aha, didn't see that one. |
@craigfoo Hi I am trying to understand how did you develop your server from where ESP was supposed to download the .bin file? If I am not wrong "http://server/file.bin" this is the server for which you would have to write a simple http code and have the bin file saved so that whenever ESP sends HTTP request from anywhere in the world, this server can respond (based on whether update is required or no?) |
@deepikavira, it's as simple as just dumping a .bin file on some server via FTP and then pointing your ESP code to that file location. There is nothing fancy on the server side. |
@craigfoo Thank you I will try it out. |
@craigfoo have you tried connecting to SFTP? Last time checked support for secured connection is still being worked on, correct me if I am wrong. |
@deepikavira, not sure about SFTP. Mine is regular ol' FTP. |
Hardware
Hardware: ESP-12 (ESP8266 Feather HUZZAH)
Core Version: 2.1.0-rc2
Description
After the .bin file is downloaded from the server, the ESP8266 reboots but gets stuck and doesn't run the new program until a physical reset happens (a button in this case on the ESP8266 Feather).
Settings in IDE
Module: ESP-12
Flash Size: 4MB
CPU Frequency: 80Mhz
Upload Using: SERIAL
Sketch
Console Output
The text was updated successfully, but these errors were encountered: