- Wed Oct 19, 2016 7:44 am
#56756
I don't know if it has been like this from the beginning (don't want to roll back my IDE) but I encountered following behaviour lately:
I forgot to make the rst-gpio16 connection on a new ESP-01 and expected to see a never waking device ... but lo and behold: I saw something on serial ?!?!?!
so the deepsleep timer can wake up the ESP on it's own!
Even the boot mode:(3,6) is correct and also is the "rst cause:5" (contrary to what one gets with rst-gpio15 connected:2)
BUT what does the "ets_main.c" mean? Why doesn't the bootloader do its thing and start the requested way (3,6)? Is it just that the 1st/2nd stage bl doesn't know whst to do with "rst cause:5" ???
For comparison a regular "reset" bootup:
any ideas? worth opening case with espressif? devs?
I forgot to make the rst-gpio16 connection on a new ESP-01 and expected to see a never waking device ... but lo and behold: I saw something on serial ?!?!?!
ets Jan 8 2013,rst cause:5, boot mode:(3,6)
ets_main.c
so the deepsleep timer can wake up the ESP on it's own!
Even the boot mode:(3,6) is correct and also is the "rst cause:5" (contrary to what one gets with rst-gpio15 connected:2)
BUT what does the "ets_main.c" mean? Why doesn't the bootloader do its thing and start the requested way (3,6)? Is it just that the 1st/2nd stage bl doesn't know whst to do with "rst cause:5" ???
For comparison a regular "reset" bootup:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v00000000
~ld
any ideas? worth opening case with espressif? devs?
