I am trying to understand how to perform some debugging.
I use Win10, Eclipse, and ESP PROG and the following kit: https://www.esp32.com/viewtopic.php?t=12307
I am followinf this : https://docs.espressif.com/projects/esp ... debugging/ and https://docs.espressif.com/projects/esp ... ure-target assuming I should use "interface/ftdi/esp32_devkitj_v1.cfg"
Yet I get an error as follow:
C:\Users\c\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190313\openocd-esp32\bin>openocd -f interface/ftdi/esp32_devkitj_v1.cfg
Open On-Chip Debugger v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
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
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
I have not changed anything to the ESP PROG firmware.
EDIT: I have flashed with Zadig software and it partially solved the first error
[SOLVED] JTAG DEBUGGING
[SOLVED] JTAG DEBUGGING
Last edited by chris007 on Thu Dec 31, 2020 3:07 am, edited 1 time in total.
Re: JTAG DEBUGGING
I have now updated the ESP PROG with winUSB driver.
My new error is now
C:\Users\c\.espressif\tools\openocd-esp32\v0.10.0-esp32-20191114\openocd-esp32\bin>openocd -f interface/ftdi/esp32_devkitj_v1.cfg
Open On-Chip Debugger v0.10.0-esp32-20191114 (2019-11-14-14:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
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: session transport was not selected. Use 'transport select <transport>'
Error: Transports available:
Error: jtag
Error: swd
Since I updated the Winusb driver with Zadig for DUAL RS232-Hs (Interface 1) and DUAL RS232-Hs (Interface 0), I don't see any allocated COM PORT to the ESP Prog in the Windows Device Manager. I only see that in the USB Peripheral "Dual RS232-HS" x 2
EDIT: Here problem while invoking openocd. Need to ask interface + board
My new error is now
C:\Users\c\.espressif\tools\openocd-esp32\v0.10.0-esp32-20191114\openocd-esp32\bin>openocd -f interface/ftdi/esp32_devkitj_v1.cfg
Open On-Chip Debugger v0.10.0-esp32-20191114 (2019-11-14-14:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
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: session transport was not selected. Use 'transport select <transport>'
Error: Transports available:
Error: jtag
Error: swd
Since I updated the Winusb driver with Zadig for DUAL RS232-Hs (Interface 1) and DUAL RS232-Hs (Interface 0), I don't see any allocated COM PORT to the ESP Prog in the Windows Device Manager. I only see that in the USB Peripheral "Dual RS232-HS" x 2
EDIT: Here problem while invoking openocd. Need to ask interface + board
Who is online
Users browsing this forum: No registered users and 268 guests