-->
Page 1 of 2

ESP8266 12F hanging after wake from Deep Sleep?

PostPosted: Tue Feb 02, 2016 3:25 pm
by lord_alan
I've been playing around with one of these ESP Witty boards I got from eBay (https://plus.google.com/+AlanLord/posts/eZHi3dkZZho).

I've had it connected up to a DHT22 for a couple of days running some LUA code which reads the sensor, sends the information to an MQTT broker then goes to deep-sleep for 5 minutes. This has been working fine up until this morning when I noticed the LED was brightly on (normally indicating the chip is powered on) but nothing is set over the UART so it looks like it has just hung.

Anyone else noticed anything like this? I did find this thread on the Espressif forum which sounds similar but clearly there is a language issue or they didn't understand what the guy was asking... http://bbs.espressif.com/viewtopic.php?t=1161

I read somewhere else that it might require a 4.7k pull up on GPIO0 and GPIO2 as well so I have just added a couple of resistors to my breadboard test to see if that makes any difference.

Re: ESP8266 12F hanging after wake from Deep Sleep?

PostPosted: Wed Feb 03, 2016 12:51 pm
by lord_alan
Nope, the 4.7K resistors didn't help :(

Here is the output of the chip on boot up:

Code: Select allNodeMCU custom build by frightanic.com
   branch: dev
   commit: fc87316b1441fa63c38eaf87d97e007f0ed078c5
   SSL: false
   modules: node,file,gpio,wifi,net,tmr,uart,mqtt,dht
 build    built on: 2016-01-27 20:52
 powered by Lua 5.1.4 on SDK 1.5.1(e67da894)
Temperature: 14.0 deg C
Humidity: 75.6%
Temperature: 14.0 deg C
Humidity: 76.6%
> Connected to MQTT
  IP: 192.168.1.168
  Port: 1883
  Client ID: esptest
  Username:
Going to deep sleep for 300 seconds

Re: ESP8266 12F hanging after wake from Deep Sleep?

PostPosted: Wed Feb 03, 2016 2:59 pm
by martinayotte
Did you attached GPIO16 to RST ?

Re: ESP8266 12F hanging after wake from Deep Sleep?

PostPosted: Wed Feb 03, 2016 3:45 pm
by lord_alan
martinayotte wrote:Did you attached GPIO16 to RST ?


Yes - as I said - it had been working for well over 24 hours, nearly 2 days... Sleeping and waking, and sleeping and waking... Then it "waked" but no data from the UART and the code didn't run so it just sat there... Not going back to sleep...