- Fri Nov 16, 2018 9:41 am
#79182
How do you know that the CPU is started after deepsleep timer expire? Is there any proof of this? It is from time to time described as an hardware bug, but I've never get more info about this.
Moderator: igrr
- Fri Nov 16, 2018 10:02 am
#79183
I will check if I get a chance, however I don't have an oscilloscope near me atm.
Pablo2048 wrote:chamathkv wrote:That should be how it works, but even though I connected GPIO16 to the RST pin, it still doesn't wake up from deep sleep. Or do anything after going to sleep for that matter. And as shown in my code, I am not using GPIO 16 for anything else either.
Can you take a look into GPIO16 and reset pin with an oscilloscope?
I will check if I get a chance, however I don't have an oscilloscope near me atm.
- Fri Nov 16, 2018 10:03 am
#79184
Well ideally, the code after deepsleep should run after the deepsleep timer is done. But absolutely nothing happens after the deepsleep code. I even tried with a very short countdown on the deepsleep timer but it still doesn't seem to help.
Pablo2048 wrote:How do you know that the CPU is started after deepsleep timer expire? Is there any proof of this? It is from time to time described as an hardware bug, but I've never get more info about this.
Well ideally, the code after deepsleep should run after the deepsleep timer is done. But absolutely nothing happens after the deepsleep code. I even tried with a very short countdown on the deepsleep timer but it still doesn't seem to help.
- Fri Nov 16, 2018 6:25 pm
#79187
@chamathkv: no, esp arduino starts with "void setup()" after deepsleep
@Pablo2048: because there is bootloader msg @74880 after deeplsleep timer expires w/o gpio16-rst
@Pablo2048: because there is bootloader msg @74880 after deeplsleep timer expires w/o gpio16-rst
