Segger J-Link fails to halt the esp32.cpu1

bobik78
Posts: 2
Joined: Tue Mar 07, 2017 4:10 am

Segger J-Link fails to halt the esp32.cpu1

Postby bobik78 » Tue Mar 07, 2017 5:20 am

Hello All,

I have ESP32 dev. board with Segger j-link as JTAG debugger.

I tried to debug ESP32 sample applications with use of OpenOCD and GDB but it failed due to "TARGET: esp32.cpui1 - Not halted" error.

Code: Select all

 ./src/openocd -s ./tcl -f ./esp32.cfg
Open On-Chip Debugger 0.10.0-dev-g90071eb (2017-03-06-11:53)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 200 kHz
force hard breakpoints
Info : No device selected, using first device.
Info : J-Link V9 compiled Apr 22 2016 11:47:06
Info : Hardware version: 9.30
Info : VTarget = 3.316 V
Info : clock speed 200 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=0x40000400
Info : accepting 'gdb' connection on tcp/3333
Info : Auto-detected RTOS: FreeRTOS
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: Core was reset (pwrstat=0x1F, after clear 0x0F).
Info : esp32.cpu0: Target halted, pc=0x40000400
esp32.cpu0: target state: halted
Error: timed out while waiting for target halted
TARGET: esp32.cpu1 - Not halted
in procedure 'reset' 
in procedure 'ocd_bouncer'
Did anyone encountered similar problem and solved it?
Any help/explanation - appreciated :)
Thanks,
Baruch

BuddyCasino
Posts: 263
Joined: Sun Jun 19, 2016 12:00 am

Re: Segger J-Link fails to halt the esp32.cpu1

Postby BuddyCasino » Tue Mar 07, 2017 8:27 am

Similar for me - I have to run the debugger shortly after powering up the board, its a narrow time window.

bobik78
Posts: 2
Joined: Tue Mar 07, 2017 4:10 am

Re: Segger J-Link fails to halt the esp32.cpu1

Postby bobik78 » Wed Mar 08, 2017 10:24 pm

This didn't work for me.
Any idea what's a problem? Is it a debugger issue or ESP32 issue?
Anyone knows?

BTW, According to ESP32 documentation -
Hardware-wise, when one CPU is halted because of debugging reasons, the other one will be halted as well; resuming also happens simultaneously.
Thanks.

Who is online

Users browsing this forum: No registered users and 302 guests