ESP8266 Developer Zone The Official ESP8266 Forum 2015-07-22T20:30:40+08:00 https://bbs.espressif.com:443/feed.php?f=6&t=562 2015-07-22T20:30:40+08:00 2015-07-22T20:30:40+08:00 https://bbs.espressif.com:443/viewtopic.php?t=562&p=2795#p2795 <![CDATA[Re: Connect GPIO16 to CHIP_PD for deep sleep mode?]]>
We have done a lot of optimizations on deep sleep in SDK lib and all optimizations are based on EST_RSTB(GPIO16---EXT_RSTB).

If you use CH_EN(GPIO16---CH_EN), then many of these optimizations can not be used each time the system restarts. Besides, the results can be unpredictable if GPIO16 is connected to CH_EN in this case.

The optimization can be summarized as below.

1) RTC memory can not be used to store data for the next wakeup.
For example, a temperature sensor to measure at the interval of 10seconds, but sent out data at the interval of 30minutes. So the firmware can store the measurement data into RTC memory, and then go to deep-sleep. At the 30min interval, the firmware send out data by WiFi.
This solution save the energy greatly, since WiFi connections need more time and more current.

2) some optimized function for deep-sleep can not be used any more, for example:
system_deep_sleep_set_option(uint8 option)
However, a new SDK in the end of July, may add more options for the applications, which may power-on rather than deep-sleep wakeup.

Thanks.

Statistics: Posted by Espressif_Kelly — Wed Jul 22, 2015 8:30 pm

]]> 2015-06-08T21:21:35+08:00 2015-06-08T21:21:35+08:00 https://bbs.espressif.com:443/viewtopic.php?t=562&p=2104#p2104 <![CDATA[Connect GPIO16 to CHIP_PD for deep sleep mode?]]>
For the convenience of PCB layout (GPIO16 / PIN 8 close to CHIP_PD / PIN 7) , we wonder whether it is possible to connect GPIO16 to CHIP_PD, other than nRESET / PIN 32, to reset the chip upon exiting deep sleep mode.

If we connect GPIO16 to nRESER pin, everything goes OK to exit the deep sleep and restart. Meanwhile, if we pull-low and then pull-high the CHIP_PD pin via an external PIO, the chip could restart successfully as well.

However, if we connect the GPIO16 to CHIP_PD (sure with a pullup to VCC as well), the boot info would be as below:

"
[b]ets Jan 8 2013,rst cause:0, boot mode:(3,6)

unknown reset
ets_main.c[/b]
"

Interesting that there is still has a notice of "ets_main.c".

What might be the cause and is there a way to avoid it and goes successfully to restart ? Any characteristic data including timing for this two pins could be shared ?

Best regards,

Statistics: Posted by Guest — Mon Jun 08, 2015 9:21 pm

]]>