OpenOCD Config Help

[satau]

Hi All,

I’m trying to configure OpenOCD debugging for ESP32. Setup is as follows:

• VisualGDB-5.2r9
• <span class=”st”>TIAO USB Multi Protocol Adapter (TUMPA)</span> v2 (VID = 0403 / PID = 8a98)
• Espressif ESP32 DevKitC

In VisualGDP ‘New Project’ I get to the ‘Debug Method’ screen. The ‘Detect’ button does not find the TIAO interface, my understanding is that I need to specify an interface script manually.

Where do I get this interface script from?

Daniel.

[satau]

Oh dear… just realized that the config file is in fact already listed in the dropdown as ‘tumpa’

So I’ve selected that, and hit ‘Test’, and I get the following output:

Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
adapter speed: 3000 kHz
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 8a98, description ‘*’, serial ‘*’ at bus location ‘*’

• This reply was modified 7 years, 11 months ago by satau.

[satau]

Ok I think it’s a USB hardware passthrough issue related to the VM that I’m running in. On bare metal I’m now seeing the following output with nothing connected to the JTAG pins:

Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 3000 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 3000 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 : esp32.cpu0: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32.cpu0: Core was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32.cpu1: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32.cpu1: Core was reset (pwrstat=0xFF, after clear 0xFF).
Info : accepting 'telnet' connection on tcp/4444
shutdown command invoked
Info : dropped 'telnet' connection

Does this look like it’s working now? Ie is this the expected output when we don’t have anything connected to the JTAG pins?

• This reply was modified 7 years, 11 months ago by satau.

[support]

Hi,

The “JTAG scan chain interrogation failed: all ones” error usually indicates a wiring issue (some of the JTAG pins are not connected properly). We would recommend starting with the ESP32 board from Sparkfun that we officially support and once you get it to work reliably, moving on to a different one.

[Author]

Posts