OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

kurta999
Posts: 13
Joined: Sat Jul 21, 2018 4:15 pm

OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

Postby kurta999 » Mon Oct 28, 2019 2:36 pm

I bougt a new ESP32 DevkitC V4 from mouser, and I'm unable to connect with openocd to it via J-TAG pin.

J-TAG wiring is OK, everything is the same as in tutorial.
https://docs.espressif.com/projects/esp ... un-openocd

OpenOCD says:
openocd -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg

Code: Select all

Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
I found somewhere that I should change those ID's to the one which is in device manager, afterwards connection still doesn't work.

Code: Select all

Error: unsupported FTDI chip type: 0x0100
Error: unable to open ftdi device with vid 10c4, pid ea60, description '*', serial '*' at bus location '*'
What I should do to made it work? Thanks!

WiFive
Posts: 2821
Joined: Tue Dec 01, 2015 7:35 am

Re: OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

Postby WiFive » Mon Oct 28, 2019 10:07 pm

What jtag adapter are you using? vid 10c4, pid ea60 is the cp2102 uart adapter, not a jtag adapter.

kurta999
Posts: 13
Joined: Sat Jul 21, 2018 4:15 pm

Re: OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

Postby kurta999 » Tue Oct 29, 2019 1:51 pm

I'm using J-Link Edu mini.

ESP_igrr
Posts: 1521
Joined: Tue Dec 01, 2015 8:37 am

Re: OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

Postby ESP_igrr » Tue Oct 29, 2019 10:25 pm

You are passing the following argument to OpenOCD: -f interface/ftdi/esp32_devkitj_v1.cfg — it tells OpenOCD that the adapter is "esp32 devkit", while in fact it is jlink. There is a jlink.cfg file in OpenOCD, maybe you can try it.

kurta999
Posts: 13
Joined: Sat Jul 21, 2018 4:15 pm

Re: OpenOCD says for ESP32 DevKitcV4: unsupported FTDI chip type: 0x0100

Postby kurta999 » Tue Dec 03, 2019 12:50 pm

That's helped thanks.

But now OpenOCD says: (with VisualGDB)
Open On-Chip Debugger 0.10.0 (2019-10-24)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 100 kHz
Info : Configured 2 cores
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 50044 for telnet connections
Error: type 'esp32' is missing virt2phys
Info : J-Link EDU Mini V1 compiled Oct 26 2018 12:05:31
Info : Hardware version: 1.00
Info : VTarget = 3.299 V
Info : clock speed 100 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32: Debug controller 0 was reset.
Info : esp32: Core 0 was reset.
Info : Listening on port 50043 for gdb connections
Info : accepting 'gdb' connection on tcp/50043
Error: No symbols for FreeRTOS
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Error: Sending data to device timed out.
Error: transport_write() failed: timeout occurred.
Error: jaylink_jtag_io() failed: timeout occurred.
Error: Failed to fetch AR regs!
Warn : Last read operation left 505 bytes.
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Error: Sending data to device timed out.
Error: transport_write() failed: timeout occurred.
Error: jaylink_jtag_io() failed: timeout occurred.
Error: Failed to fetch AR regs!
Info : Target halted. CPU0: PC=0x00000000 (active)
Warn : Last read operation left 505 bytes.
Info : Target halted. CPU1: PC=0x00000000
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Warn : Failed to send data to device: LIBUSB_ERROR_TIMEOUT.
Error: Sending data to device timed out.
Any ideas? I already googled a lot but nothing worked. It's a DevKitC with J-Link EDU.
Wiring is based on this image, is this correct? https://1.bp.blogspot.com/-RL8tkZprmjc/ ... pinout.png

Who is online

Users browsing this forum: Bing [Bot] and 18 guests