Waking up from deep sleep without a connection between GPIO16 and RST?

[jayeye]

Please help me understand deep sleep behavior better.

When, as recommended, I connect GPIO16 to the RST pin (in case in matters: on an Adafruit HUZZAH (ESP-12) board; using the Arduino environment), the processor does indeed wake up, but its behavior is identical to a reset (I get the following on the debug UART:

Code: Select all

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld


Which is exactly what I get when I simply reset the board.

Q1: Is this the expected behavior? If so, what is the point of specifying the RF behavior after wakeup, since the processor resets anyway?

Q2: What really happens if I don't connect GPIO16 to RST? What I get from the debug UART is just:

Code: Select all

ets_main.c


Not even a CRLF. What does this really mean?

Thanks in advance

/ji

[Espressif_Kelly]

Hi,

We test with ESP-12-Q and didn't replicate your issue. After wake-up, the programme runs ok.

About deep sleep wake-up, GPIO16(RTC_IO) will give low level signal to EXT_RSTB to reset the module. That's why we request GPIO16 to be connected to EXT_RSTB.

Could you please send us your test bin files that can be used to reproduce this problem?

Thanks.