Debug controller reset when including a method in source

mazorsk
Posts: 8
Joined: Mon Aug 24, 2020 1:49 pm

Debug controller reset when including a method in source

Postby mazorsk » Mon Aug 24, 2020 1:55 pm

Hello good people of espia
I have encountered a weird issue while debugging my software (using jtag ft2232hl), the code is written in C++..
What is happening is when i add the call to "esp_err_t err = esp_http_client_perform (client);"
and start debugging then the output given to me is

Info : esp32.cpu0: Debug controller was reset.
esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.

and being repeated, when i comment out the call to 'esp_http_client_perform' the debug works as proper and i can step through the code
Would love some assistance, Thanks in advance!

ESP_igrr
Posts: 2071
Joined: Tue Dec 01, 2015 8:37 am

Re: Debug controller reset when including a method in source

Postby ESP_igrr » Mon Aug 24, 2020 11:14 pm

Hi mazorsk, could you check what is printed on the UART output when "Debug controller was reset" is printed in the debugger?

mazorsk
Posts: 8
Joined: Mon Aug 24, 2020 1:49 pm

Re: Debug controller reset when including a method in source

Postby mazorsk » Sun Aug 30, 2020 11:52 am

Hi, thank you for the fast reply.. im not sure what you mean by uart monitor (no such window in visualgdb)
i have the openocd output, again - this only happens when i include the mentioned method in the source..
thanks again

C:\Users\trakt\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c "gdb_port 56102" -c "telnet_port 56
101" -f interface/ftdi/esp32_devkitj_v1.cfg -c "adapter_khz 3000" -f target/esp32.cfg -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.10.0 (2020-07-22)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

adapter speed: 3000 kHz

Info : FreeRTOS creation
Info : FreeRTOS creation
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 56101 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 3000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Target halted, PC=0x4007985E, debug_reason=00000000
Info : Listening on port 56102 for gdb connections
Info : accepting 'gdb' connection on tcp/56102
Warn : No symbols for FreeRTOS!
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : Set GDB target to 'esp32.cpu0'
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 197 KB
Info : Flash mapping 1: 0x50020 -> 0x400d0020, 739 KB
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : Auto-detected flash bank 'esp32.cpu0.flash' size 4096 KB
Info : Using flash bank 'esp32.cpu0.flash' size 4096 KB
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 197 KB
Info : Flash mapping 1: 0x50020 -> 0x400d0020, 739 KB
Info : Using flash bank 'esp32.cpu0.irom' size 740 KB
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 197 KB
Info : Flash mapping 1: 0x50020 -> 0x400d0020, 739 KB
Info : Using flash bank 'esp32.cpu0.drom' size 200 KB
Info : New GDB Connection: 1, Target esp32.cpu0, state: halted
force hard breakpoints
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
** Programming Started **
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
** Programming Finished **
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
** Programming Started **
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
** Programming Finished **
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
** Programming Started **
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
Info : esp32.cpu0: Target halted, PC=0x40091856, debug_reason=00000001
** Programming Finished **
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.

mazorsk
Posts: 8
Joined: Mon Aug 24, 2020 1:49 pm

Re: Debug controller reset when including a method in source

Postby mazorsk » Sun Aug 30, 2020 12:28 pm

hi, i managed to step into some panic handler (wrapped the client_perform method with try/catch but to no avail)
0x3ffbc83b "abort() was called at PC 0x4015c6a3 on core 0" {97 'a'}
hopes this could help somehow

Iron1990
Posts: 1
Joined: Sun Jan 08, 2023 7:33 am

Re: Debug controller reset when including a method in source

Postby Iron1990 » Sun Jan 08, 2023 7:47 am

Hi!

So I Have This Issue too and i know solution for this.

So if you follow tutorial i found https://www.instructables.com/How-to-U ... -an-ESP32/.

First you must add line into platformio.ini
upload_protocol = esp-prog
Than You must change board in config i am using board = esp32dev

Than if you are using dev-kit you must connect GND cable to GND on ESP32 BOARD but only if you connected ESP-PROG via USB

also you can`t define port like debug_port = COM4 thats making issue.


Also if you downloaded platformio OpenOCD is included

Who is online

Users browsing this forum: No registered users and 245 guests