Is it possible to use ESP8266's OTA capabilities?
-
@tekka did you changed any of the standard settings for ESP flashing? I simply updated ESP8266 library and reflashed, but I get an reboot loop. In the serial monitor I see:
0‚~?–4“Ò¶£ÿOAaû0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) 0;255;3;0;9;Radio init successful. scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 2 cnt connected with mDjEKlujYacByG5JtxlY, channel 1 ip:192.168.38.19,mask:255.255.255.0,gw:192.168.38.1 .IP: 192.168.38.19 ¥üÊæ” ×Åü1¤ñþ0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) 0;255;3;0;9;Radio init successful. scandone state: 0 -> 2 (b0)When going back to 2.0.0 it works without problems. Here my settings for flashing:

-
@tekka did you changed any of the standard settings for ESP flashing? I simply updated ESP8266 library and reflashed, but I get an reboot loop. In the serial monitor I see:
0‚~?–4“Ò¶£ÿOAaû0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) 0;255;3;0;9;Radio init successful. scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 2 cnt connected with mDjEKlujYacByG5JtxlY, channel 1 ip:192.168.38.19,mask:255.255.255.0,gw:192.168.38.1 .IP: 192.168.38.19 ¥üÊæ” ×Åü1¤ñþ0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) 0;255;3;0;9;Radio init successful. scandone state: 0 -> 2 (b0)When going back to 2.0.0 it works without problems. Here my settings for flashing:

-
I'm trying to use the serial monitor but I'm always ask entering a password? Although I didn't used one?
Reflashing sketch via OTA worked without any issues.
Edit: Tried to use a real OTA password and it's still not working although I'm using the correct. ESP8266 Tools 2.2.0
-
to my last knowledge this feature is implemented but not working. If you want to see the serial monitor you have to connect physically.
Regarding the bootloops: how you structure your code seems to have an effect. If you have busy-waits in your code, you're more likely to encounter the WDT timeout. I restructured my code to be more interrupt driven and to complete more frequent cycles through the main loop(). After doing that, the WDT timeouts stopped.
That said, I don't know whether your bootloop is caused by a WDT timeout or something else. At least in my case, the debug messages being printed in the serial window specifically mentioned WDT being involved.
-
I presume debugging via network is not supported, I read some posts on Github but couldn't be sure if it was implemented?
-
I presume debugging via network is not supported, I read some posts on Github but couldn't be sure if it was implemented?
By debugging, do you mean looking at the serial console output over the network, or something else?
-
By debugging, do you mean looking at the serial console output over the network, or something else?
@NeverDie said:
By debugging, do you mean looking at the serial console output over the network, or something else?
Yes, serial monitor via network within IDE...