FYI, the relevant comments in Kconfig were changed a couple weeks after your question, so it looks like the hardware guide and code now agree that you should connect it to 32K_XN. https://github.com/espressif/esp-idf/commit/a50966cf7a9253fa1758e3927e0e2cd550ef8769 edit: However, they still disagree ...

Try This is needed because, by default, the RTC_PERIPH power domain (IO, sensors, ULP) will only be enabled if you're using one of them as a wakeup source.

So you want CTS/DTR instead of RTS/DTR? I can't test that easily here, but try the cts-dtr branch on github. Connect CTS to EN and DTR to IO0/BOOT.

Jim

This looks like the same issue as
https://github.com/espressif/esp-idf/issues/3107
https://github.com/espressif/esp-idf/issues/3112
https://github.com/espressif/esp-idf/issues/3020

Sending continuous ping requests (every 1s) prevents the station from being disconnected, but I would prefer not to have to do this.

Explicitly calling esp_wifi_set_ps(WIFI_PS_NONE), rather than leaving at the default WIFI_PS_MIN_MODEM, does not help.

Any suggestions?

I'm having a problem where my ESP32 disconnects from the WiFi access point after 110 seconds. It always reconnects just fine a few seconds later. The typical sequence is: Scan for APs, connect, immediately send a SNTP and HTTP request, get responses within a few seconds, then wait. After 110 seconds...

I have a FTDI USB-to-serial adapter that only brings out TX, RX, RTS, and CTS, so I hooked it up directly to the ESP32 as follows: RTS --> EN CTS --> IO0/BOOT TX --> RXD0 RX <-- TXD0 Then I wrote a esptool.py wrapper that makes it work, via libftdi & switching in and out of bitbang mode as needed: h...