Strange problem with reconnects
Posted: Mon Jan 12, 2015 5:03 pm
Hi,
I was trying to develop a simple temperature and humidity logger using esp8266 and dht22. Everything went smoothly, I had a version which worked for over 2 weeks and logged everything nicely, going into deep sleep between readings. Than, I started to add new features and suddenly my esp stopped connecting to the wi-fi network. As far as I can tell, radio is working, but IP address is not requested from the DHCP server. I thought, that maybe my binary is to big or something like that - anyway, I got back to the source version, which was working OK for me. And the problem didn't stop! No matter what software version I flash (I even tried other firmwares), my ESP is starting (I can see DBG messages from my init function, but never connects to the INternet. The actual log is
and so on. What can be wrong? Any ideas? How can I debug this further? How do you cope with error handling at all?
Thanks for any help.
I was trying to develop a simple temperature and humidity logger using esp8266 and dht22. Everything went smoothly, I had a version which worked for over 2 weeks and logged everything nicely, going into deep sleep between readings. Than, I started to add new features and suddenly my esp stopped connecting to the wi-fi network. As far as I can tell, radio is working, but IP address is not requested from the DHCP server. I thought, that maybe my binary is to big or something like that - anyway, I got back to the source version, which was working OK for me. And the problem didn't stop! No matter what software version I flash (I even tried other firmwares), my ESP is starting (I can see DBG messages from my init function, but never connects to the INternet. The actual log is
Code: Select all
add if0
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
add if1
bcn 100
scandone
add 0
aid 2
pm open phy_2,type:2 0 0
cnt
DBG: reset counter 0/1
DBG: reset counter 0/2
Continuing normal boot
starting config mode
TCP config server init, conn=0x3ffea018
rm match
pm close 7 0 0/4240083
reconnect
scandone
add 0
aid 2
pm open phy_2,type:2 0 0
cnt
rm match
pm close 7 0 0/4007647
reconnect
...
and so on. What can be wrong? Any ideas? How can I debug this further? How do you cope with error handling at all?
Thanks for any help.