Page 1 of 1

openocd jtag problem [solved]

Posted: Mon Jan 21, 2019 10:36 pm
by michaelu
Hi,
I use Sloeber, and try to debug with an OpenOCD Jtag adapter.
In Eclipse, the GDB OpenOCD Debugging Config options are

Code: Select all

-c "debug_level 3" -s d:/eclipse-sloeber/openocd-esp32/share/openocd/scripts -f interface/ftdi/openocd-usb.cfg -f board/esp-wroom-32.cfg -c "adapter_khz 1000"
When I start to debug, Eclipse pops up a "Problem Occurred" window, with details:

Code: Select all

Error in final launch sequence
Failed to execute MI command:
continue
Error message from debugger back end:
Warning:\nCannot insert breakpoint 1.\nCannot access memory at address 0x400d2674\nCannot insert breakpoint 2.\nCannot access memory at address 0x400f1aec\n
Failed to execute MI command:
continue
Error message from debugger back end:
Warning:\nCannot insert breakpoint 1.\nCannot access memory at address 0x400d2674\nCannot insert breakpoint 2.\nCannot access memory at address 0x400f1aec\n
Warning:\nCannot insert breakpoint 1.\nCannot access memory at address 0x400d2674\nCannot insert breakpoint 2.\nCannot access memory at address 0x400f1aec\n
...

[/code]

Re: openocd jtag problem

Posted: Tue Jan 22, 2019 1:55 am
by ESP_igrr
Could you please post the messages related to failure to get flash mappings (at -d3 debug level)? They might point to the source of the issue — without knowing flash layout, OpenOCD can not insert breakpoints in flash.

Re: openocd jtag problem

Posted: Wed Jan 23, 2019 8:28 pm
by michaelu
Sorry that I bothered you with this. I think the problem was the "adapter_khz 1000" at the end of the config options, where a 0 is missing. Also, the statement is not necessary, esp32.cfg contains an "adapter_khz 20000" statement.