Inline debugging ESP32 beyond deep sleep ?

Hello everybody,
I try to debug beyond deep sleep. I have one breakpoint set at esp_deep_sleep(1000000 * 10). It is hit and I can step until esp_deep_sleep_start() is called. The MCU is regularly active, and I can monitor its output which is sent over telnetstream. Albeit obviously running, the debugger never stops again, seemingly ignorig breakpoints set wherever in my code (and eaqually not in void RTC_IRAM_ATTR esp_wake_deep_sleep(void) at esp_default_wake_deep_sleep().
I whouldn’t expect debugging to survive deep sleep, but I see on the debug console these lines:

Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
esp32.cpu0: Debug controller was reset.
esp32.cpu0: Core was reset.
Info : esp32.cpu0: Detected debug stubs @ 3ffc24b0
esp32.cpu0: Detected debug stubs @ 3ffc24b0

looping in 10 sec inteval, suggesting that some debugging stubs may have survived and may be accessible for further inline debugging.
Can someone please offer hints to achieve this? Thanks for your time.


debian 10.8, VSCode 1.53.2, PIO Core 5.1.0, Home 3.3.3, ESP-Prog,
platformio.ini with
platform = GitHub - platformio/platform-espressif32: Espressif 32: development platform for PlatformIO
board = featheresp32
framework = arduino
upload_protocol = esp-prog
upload_port = /dev/ttyUSB_prog
monitor_port = /dev/ttyUSB_jtag

This question seems better off if asked at Issues · espressif/openocd-esp32 · GitHub directly. The Espressif people should know their chip and debugger and should be able to help you.

1 Like

Thanks for your hint. See