I have a problem that is a little bizarre. I have been using a piece of code that wakes up, does what it needs to do, and then goes to sleep for 1 hour.
This used to work perfectly until I had to move PCs and packed everything into a VM (could not use git or anything). Now I am running the same code on my boards but it does not wake up anymore.
After a little debugging I noticed that it rebooted itself correctly after a WDT reset. I could use the sdk_system_restart function and it works correctly (after a power cycle....esptool v1.2), but it doesn't work for sdk_system_deep_sleep. I did a power cycle and nothing, it runs smoothly the first time but it does not come back to life. I did another power cycle and monitored the serial output at 74468 baud to check what was the microcontroller's output during boot time.
When booting the first time it outputs the following:
And after it runs the deep sleep command, it runs the following boot log:
ets Jan 8 2013,rst cause:5, boot mode:(3,6)
ets_main.c
It seems to me that it's jumping to an incorrect address when booting. This might mean that I'm either using the wrong binary files (config_blank, rboot, etc) or I'm loading them in the wrong addresses
Hello,
I have a problem that is a little bizarre. I have been using a piece of code that wakes up, does what it needs to do, and then goes to sleep for 1 hour.
This used to work perfectly until I had to move PCs and packed everything into a VM (could not use git or anything). Now I am running the same code on my boards but it does not wake up anymore.
After a little debugging I noticed that it rebooted itself correctly after a WDT reset. I could use the sdk_system_restart function and it works correctly (after a power cycle....esptool v1.2), but it doesn't work for sdk_system_deep_sleep. I did a power cycle and nothing, it runs smoothly the first time but it does not come back to life. I did another power cycle and monitored the serial output at 74468 baud to check what was the microcontroller's output during boot time.
When booting the first time it outputs the following:
And after it runs the deep sleep command, it runs the following boot log:
It seems to me that it's jumping to an incorrect address when booting. This might mean that I'm either using the wrong binary files (config_blank, rboot, etc) or I'm loading them in the wrong addresses