GDB stopped working for ESP32 Arduino

[felixcollins]

I Have been using VGDB with a Tumpa Lite board to work with an ESP32 Wroom Module on a custom board. Everything has been fine. Today I tried a custom partitions.csv in the sketches folder. Now I can’t program the ESP32 over JTAG anymore. I’ve taken the partitions.csv file back out and done a clean and rebuild. But it still fails. Does anyone know what might be stuck? In particular what does the message @”not enough working area available(requested 10433)\n” @”no working area available, can’t alloc space for stub code!\n” mean?  Is this space in the flash? Or in the PC memory? Or where?

Thanks,

Felix

mon program_esp "C:/Users/felix/AppData/Local/Arduino15/packages/esp32/hardware/esp32/1.0.6/tools/sdk/bin/bootloader_qio_80m.bin" 0x1000
&"mon program_esp \"C:/Users/felix/AppData/Local/Arduino15/packages/esp32/hardware/esp32/1.0.6/tools/sdk/bin/bootloader_qio_80m.bin\" 0x1000\n"
@"JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
@"JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
@"esp32.cpu0: Debug controller was reset.\n"
@"esp32.cpu0: Core was reset.\n"
@"esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000\n"
@"esp32.cpu0: Core was reset.\n"
@"esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000\n"
@"esp32.cpu1: Debug controller was reset.\n"
@"esp32.cpu1: Core was reset.\n"
@"esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000\n"
@"** Programming Started **\n"
@"timed out while waiting for target halted / 4 - 2\n"
@"esp32.cpu0: Target halted, PC=0x40090369, debug_reason=00000000\n"
@"xtensa_wait_algorithm: not halted 0, pc 0x40090369, ps 0x60025\n"
@"Failed to wait algorithm (-302)!\n"
@"Algorithm run failed (-302)!\n"
@"not enough working area available(requested 10433)\n"
@"no working area available, can't alloc space for stub code!\n"
@"not enough working area available(requested 10433)\n"
@"no working area available, can't alloc space for stub code!\n"
@"** Programming Finished **\n"
^done
mon program_esp "C:/Users/felix/source/Thor/fw-10320-sensor-hub-esp32-firmware/FW-10320-sensor-hub-esp32-FW/Output/ESP32_Dev_Module/Debug/FW-10320-Sensor-Hub-ESP32-FW.ino.bin" 0x10000
&"mon program_esp \"C:/Users/felix/source/Thor/fw-10320-sensor-hub-esp32-firmware/FW-10320-sensor-hub-esp32-FW/Output/ESP32_Dev_Module/Debug/FW-10320-Sensor-Hub-ESP32-FW.ino.bin\" 0x10000\n"
@"JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
@"JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
@"esp32.cpu0: Debug controller was reset.\n"
@"esp32.cpu0: Core was reset.\n"
@"esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000\n"
@"esp32.cpu0: Core was reset.\n"
@"esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000\n"
@"esp32.cpu1: Debug controller was reset.\n"
@"esp32.cpu1: C

[support]

Hi,

This looks like a message coming from the ESP32 OpenOCD port that is maintained by Espressif. Most likely, some changes to the project configuration are either incompatible with JTAG debugging, or trigger a bug in OpenOCD.

Our best advice would be to try erasing the FLASH memory via esptool.py and reverting the change that triggered it. If you need further help with this, please consider submitting a bug to the ESP32 OpenOCD repository on Github.

[felixcollins]

Yay! Thanks for the advice. Erasing the whole flash using esptool got JTAG working again.

[Author]

Posts