Still Windows JTAG debugging issues
Posted: Mon Feb 22, 2021 9:15 pm
After speding days attempting to get JTAG debugging working (VSCODE), I decided to give Eclipse a try.
With Eclipse experiencing similar issues, device is detected via JTAG and that's were it ends.
I am using the Lyra-T board. Can there be any hardware related issue causing debug problems, while JTAG device detection always seems to work reliable ?
Somehow for many people JTAG debugging seems to be a problem, so what can be wrong here ?
Any suggestions are welcome.
With Eclipse experiencing similar issues, device is detected via JTAG and that's were it ends.
I am using the Lyra-T board. Can there be any hardware related issue causing debug problems, while JTAG device detection always seems to work reliable ?
Somehow for many people JTAG debugging seems to be a problem, so what can be wrong here ?
Any suggestions are welcome.
.. then nothingOpen On-Chip Debugger v0.10.0-esp32-20200709 (2020-07-09-08:54)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz
Warn : Interface already configured, ignoring
Info : Configured 2 cores
Started by GNU MCU Eclipse
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
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 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 : Target halted. CPU0: PC=0x40090910 (active)
Info : Target halted. CPU1: PC=0x40000400
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Error: No symbols for FreeRTOS