This behavior seems to be related to calling nvs_commit() before going to sleep. The timestamp of the TG1WDT reset is immediately after attempting sleep. I suspect that writing to flash immediately before going to sleep sometimes causes the TG1WDT to time out and fire a reset. Ignore that. I just s...

Every once in a while, we're seeing esp32 being woken up by TG1WDT_SYS_RESET. From the logs below, you can see the device wakes up once as expected from DEEPSLEEP_RESET, then goes to sleep and is woken up by TG1WDT_SYS_RESET, goes to sleep again, and then woken up normally by DEEPSLEEP_RESET. Deep s...

I believe one of the recent commits (RTC overflow) fixed the timing issue.

Running with external 32kHz didn't seem to help.

The issue seems to be most prominent when device is in motion. When I had the device sitting on my desk overnight, they timestamps were all within 5 seconds of expected 5 mins. But when I took the device with me on my skateboard ride, the wake ups would occur at random intervals between 0 and 5 mins...

We do. We're also ran this with RTC clock set to internal.

I'm seeing weird behavior from the deep sleep timer. Setup: 1. Using pretty much the exact same circuit as Sparkfun's ESP32 Thing (https://www.sparkfun.com/products/13907), except we have Rev 1 of silicon. 2. ESP-IDF as of June 12, 2017 3. Wake up, perform wifi scan, record data (including current R...

ESP_igrr wrote: you do need this pullup, and the software also has to send powerdown command to the flash chip before entering deep sleep.

It seems to be working without the powerdown command? How necessary is that command and is there an API to do that?

ESP32 Thing by Sparkfun. Which board are you using?

Just a heads up, many boards (including ESP32 WROOM, at least from the schematics available) do not have a pull-up on flash /CS line. This means that when the ESP32 goes to sleep and GPIO is turned off, the /CS line is floating. This prevents the flash from going to standby mode. For my custom board...