FTDI DEXT installation : Open OCD fails on MAC OS 11.5.2 (OCD-407)

[rohiniramegowda]

Environment

• Development Kit: ESP WROVER E
• Module or chip used: ESP WROVER
• Debug Adapter: ESP-PROG
• OpenOCD version: [v0.10.0-esp32-202104012]
• Operating System: MAC OS 11.5.2
• Using an IDE?: NO
• OpenOCD command line: openocd -f board/esp32-wrover-kit-3.3v.cfg]
• JTAG Clock: 2000
• ESP-IDF version: 4.2

Problem Description

Steps to reproduce the behavior:
Hi ,

I am trying to setup the debugger on ESP WROVER E Kit and I have ESP Prog . I realized that this version of mac does not support kext but dext. I have the beta version downloaded from site and ran it in my application folder .

I have the port recognized as

cu.usbserial-14220
cu.usbserial-1423100
cu.usbserial-1423101

tty.usbserial-14220
tty.usbserial-1423100
tty.usbserial-1423101

When I run open OCD I still get the below error . I am trying this on Command line. Am I missing something ? Is there any documentation I can refer to ?

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
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 zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

[igrr]

Error: esp32.cpu0: IR capture error; saw 0x00 not 0x01 usually means that at least some of JTAG lines aren't properly connected between the debug probe and the chip, or the software running on the chip has reconfigured the JTAG pins for some other purpose (e.g. SPI or SDMMC).

Could you check if 4 JTAG jumpers are installed as shown in https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit.html#setup-options?

To make sure that the application is not reconfiguring any of the JTAG pins for a different purpose, could you try flashing e.g. the blink example before starting the debugging session?

[rohiniramegowda]

I am trying to debug hello_world example. I checked the connections and they seem fine . I am using the connections below . I loaded the com.ftdi.vcp.dext from DriverExtensions folder and after that its able to recognize one of the port I guess but I am still getting this error

MTDO / GPIO15 | TDO
MTDI / GPIO12 | TDI
MTCK / GPIO13 | TCK
MTMS / GPIO14 | TMS
GND | GND

Info : JTAG tap: esp32.cpu0 tap/device found: 0x00000001 (mfg: 0x000 (), part: 0x0000, ver: 0x0)
Warn : JTAG tap: esp32.cpu0 UNEXPECTED: 0x00000001 (mfg: 0x000 (), part: 0x0000, ver: 0x0)
Error: JTAG tap: esp32.cpu0 expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : TAP esp32.cpu1 has invalid IDCODE (0x0)
Info : TAP auto0.tap has invalid IDCODE (0x0)
Info : TAP auto1.tap has invalid IDCODE (0x0)
Info : TAP auto2.tap has invalid IDCODE (0x0)
Info : TAP auto3.tap has invalid IDCODE (0x0)
Info : TAP auto4.tap has invalid IDCODE (0x0)
Info : TAP auto5.tap has invalid IDCODE (0x0)
Info : TAP auto6.tap has invalid IDCODE (0x0)
Info : TAP auto7.tap has invalid IDCODE (0x0)
Info : TAP auto8.tap has invalid IDCODE (0x0)
Info : TAP auto9.tap has invalid IDCODE (0x0)
Info : TAP auto10.tap has invalid IDCODE (0x0)
Info : TAP auto11.tap has invalid IDCODE (0x0)
Info : TAP auto12.tap has invalid IDCODE (0x0)
Info : TAP auto13.tap has invalid IDCODE (0x0)
Info : TAP auto14.tap has invalid IDCODE (0x0)
Info : TAP auto15.tap has invalid IDCODE (0x0)
Info : TAP auto16.tap has invalid IDCODE (0x0)
Info : TAP auto17.tap has invalid IDCODE (0x0)
Info : TAP auto18.tap has invalid IDCODE (0x0)
Warn : Unexpected idcode after end of chain: 52 0x00000000
Warn : Unexpected idcode after end of chain: 84 0x00000000
Warn : Unexpected idcode after end of chain: 116 0x00000000
Warn : Unexpected idcode after end of chain: 148 0x00000000
Warn : Unexpected idcode after end of chain: 180 0x00000000
Warn : Unexpected idcode after end of chain: 212 0x00000000
Warn : Unexpected idcode after end of chain: 244 0x00000000
Warn : Unexpected idcode after end of chain: 276 0x00000000
Warn : Unexpected idcode after end of chain: 308 0x00000000
Warn : Unexpected idcode after end of chain: 340 0x00000000
Warn : Unexpected idcode after end of chain: 372 0x00000000
Warn : Unexpected idcode after end of chain: 404 0x00000000
Warn : Unexpected idcode after end of chain: 436 0x00000000
Warn : Unexpected idcode after end of chain: 468 0x00000000
Warn : Unexpected idcode after end of chain: 500 0x00000000
Warn : Unexpected idcode after end of chain: 532 0x00000000
Warn : Unexpected idcode after end of chain: 564 0x00000000
Warn : Unexpected idcode after end of chain: 596 0x00000000
Warn : Unexpected idcode after end of chain: 628 0x00000000
Error: double-check your JTAG setup (interface, speed, ...)
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu1: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors

[erhankur]

@rohiniramegowda Closing this. If you still have an issue, feel free to re-open.