ESP32 Forum

Hi,

I bought a tumpa V2 Jtag adapter.
I’ve tried to use it under windows 7 and Linux Ubuntu 18.04, but the Jtag interface is not detected in both case.

Under windows, I’ve downloaded the ftdi drivers and installed it with Zadig. Interface 0 & 1 seems to work properly when I look the device manager, but when I’m running openocd, I have an lib_usb_open error.

Under Linux, I’ve downloaded the ftdi drivers (v 1.4.8) and installed it as recommandés by ftdi. Using lsbus et lsmod i can’t seen that the board it detected, but using openocd, same problem, the Jtag interface can’t be open.

So, I’ve read that espressif used internally some tumpa adapter, please can you share the step-by-step process to configure a tumpa at least under Linux to use with openocd ?

I left the tumpa jumpers on the board with the default positions, maybe some jumpers needs to be moved (if you have some photo, it will be kind to share) ?

Thank you in advance for your help.

Regards.

Not sure about Windows, but Linux does not need any drivers installed (and possibly installing the FTDI drivers broke your setup). Can you post the specific OpenOCD output?

Hello,

Thanks for your reply,

when I plug my tumpa, lsysb gives me :

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 009: ID 0403:8a98 Future Technology Devices International, Ltd TIAO Multi-Protocol Adapter
Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

So it seems that my tumpa is recognize by the system.

When I launch, udevadm -k -p, I obtain the following when I plug my tumpa

KERNEL[5833.405485] add /devices/pci0000:00/0000:00:1a.7/usb1/1-5 (usb)
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/011
DEVNUM=011
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5
DEVTYPE=usb_device
MAJOR=189
MINOR=10
PRODUCT=403/8a98/700
SEQNUM=3259
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[5833.409499] add /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v0403p8A98d0700dc00dsc00dp00icFFiscFFipFFin00
PRODUCT=403/8a98/700
SEQNUM=3260
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[5833.412615] add /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v0403p8A98d0700dc00dsc00dp00icFFiscFFipFFin01
PRODUCT=403/8a98/700
SEQNUM=3261
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[5833.415331] add /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0 (usb-serial)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0
SEQNUM=3262
SUBSYSTEM=usb-serial

KERNEL[5833.416658] add /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0/tty/ttyUSB0 (tty)
ACTION=add
DEVNAME=/dev/ttyUSB0
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0/tty/ttyUSB0
MAJOR=188
MINOR=0
SEQNUM=3263
SUBSYSTEM=tty

KERNEL[5833.427379] bind /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0 (usb-serial)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1/ttyUSB0
DRIVER=ftdi_sio
SEQNUM=3264
SUBSYSTEM=usb-serial

KERNEL[5833.430574] bind /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1 (usb)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.1
DEVTYPE=usb_interface
DRIVER=ftdi_sio
INTERFACE=255/255/255
MODALIAS=usb:v0403p8A98d0700dc00dsc00dp00icFFiscFFipFFin01
PRODUCT=403/8a98/700
SEQNUM=3265
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[5833.432569] bind /devices/pci0000:00/0000:00:1a.7/usb1/1-5 (usb)
ACTION=bind
BUSNUM=001
DEVNAME=/dev/bus/usb/001/011
DEVNUM=011
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-5
DEVTYPE=usb_device
DRIVER=usb
MAJOR=189
MINOR=10
PRODUCT=403/8a98/700
SEQNUM=3266
SUBSYSTEM=usb
TYPE=0/0/0

And when I lauch Openocd :

Open On-Chip Debugger v0.10.0-esp32-20190313 (2019-03-13-09:52)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
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 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

Looks like OpenOCD detected and configured an adapter; unless you have other jtag adapters connected to your machine I'm going to assume it's the Tumpa. However, it can't see the ESP32. Are you sure it's connected properly, and that any application you may have running on the ESP doesn't reconfigure the JTAG gpios (12-15) to something else?

Hello,

I was probably a little bit tired.

In fact I was a problem of wiring between my tumpa and my ESP32 board.

All is working properly now and effectively the installation of the D2xx ftdi driver is not mandatory under linux (i'm working on ubuntu 18.04 LTS). ftdi_sio & usbserial drivers are working fine.

Thank you for your help.