Can't really help anyoen - the idf-openocd debugger don't work

[BergLoewe]

Hello,


I've difficulties with the dubugger. I tried it in VSCode
viewtopic.php?f=40&t=19050

I tried it in Eclipse - see picture.

How works the dubugging for esp-idf?

[BergLoewe]

If I try to start the openocd with cmd.exe I get ths answer:

Code: Select all

c:\ESP32\.espressif\tools\openocd-esp32\v0.10.0-esp32-20200709\openocd-esp32\bin>openocd -f board/esp32-wrover-kit-3.3v.cfg
Open On-Chip Debugger  v0.10.0-esp32-20200709 (2020-07-09-08:54)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : Configured 2 cores
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

and then the cmd.exe hangs up.
I found ths site:
https://docs.espressif.com/projects/esp ... un-openocd

This speaks about libusb. I think that means the driver. I did install the driver with zadig.

Code: Select all

Error: JTAG scan chain interrogation failed: all ones

What ca I do for this?

Code: Select all

Error: Check JTAG interface, timings, target power, etc.

I've a wrover Kit v3 and I've connect the jumpers like here:
https://docs.espressif.com/projects/esp ... up-options

Code: Select all

Error: Trying to use configured scan chain anyway...

How can I configure the scan chain? Where I can find that?

[ESP_Sprite]

Your software seems all in order. That error is something you get when there is something wrong between the JTAG adapter and the chip. Can it be that you have software running on the devboard that reconfigures GPIO12-15 to something else? That breaks JTAG communication as those GPIOs are the ones the JTAG signal normally is on.

[BergLoewe]

Thank you very mutch, @ESP_Sprite!

I really had used pins of GPIO12-15.
But I still did not get ahead.

I used then the hello_world example. The result was the same. I found this site:
https://docs.espressif.com/projects/esp ... ugger.html
and worked trought that. But on the question of target is fini. This document doesn't allow a seial or USB connection. Now I have in the debug config the option 'ESP-IDF GDB OpenOCD Debugging and I maked here the same like in the document. But in the tab 'Debugger" he offers a GDB port.

But the result you can see in the picture.

[ESP_Sprite]

Well, openocd works like a charm - that looks like a good JTAG connection. However, I'm not sure what you have connected to OpenOCD but it looks like that is expecting an ARM CPU somehow, not an Xtensa. Are you sure that whatever you're trying to do the debugging with supports and is configured for the ESP32?

[BergLoewe]

Thanks a lot!

You are not sure - I' no also. Sorry, I'm a beginner about ESP. And then the problems with the language.
Well, where I can see how adjust the JATAG in the Eclipse?

Thank you for your help!