Moderator: Sprite_tm
dzindra wrote:Same thing happened to me too, but I do not think It is caused by closing connection early. I managed to get rid of it by flashing blank.bin and default init data present in IoT SDK.
Also if you keep GPIO0 low for 5 seconds esphttpd switches to AP+STA mode and reboots ESP - in my expirience this usually is the cause of broken init data and described behaviour. You might want to comment it out in io.c
I've tried re-flashing those bins using "make flashinit" but it didn't make a difference. GPIO0 is tied to Vcc, so it can't be that either. What version of the SDK are you using? I tried 1.0.0 and 1.0.1 with bad results. I will try using older versions.
Sprite_tm wrote:Also, do you use the most recent version of esphttpd as pulled from my Git repo?
Yes, I refreshed from http://git.spritesserver.nl/esphttpd.git. Is that the latest? Or is https://github.com/bjpirt/esphttpd more up to date?
Ovaltineo wrote:Sprite_tm wrote:Also, do you use the most recent version of esphttpd as pulled from my Git repo?
Yes, I refreshed from http://git.spritesserver.nl/esphttpd.git. Is that the latest? Or is https://github.com/bjpirt/esphttpd more up to date?
The spritesserver.nl link indeed is the latest version; bjpirt maintains a fork with stuff that should eventually be merged in the mainline. I actually have seen the reconnects before, but I kinda assumed it was bad hardware or reception; esphttpd itself does nothing specific to reconnect to an AP.