Help debugging ESP32 WROOM with jlink edu mini

PaulELong
Posts: 14
Joined: Thu Oct 24, 2019 9:47 pm

Help debugging ESP32 WROOM with jlink edu mini

Postby PaulELong » Fri Nov 08, 2019 6:25 pm

I'm trying to setup a debugging, but OpenOCD fails to connect and repeats the warning "Failed to receive data from device: LIBUSB_ERROR_TIMEOUT." Then I see Error: Sending data to device timed out. I'll put the full output below.

The steps I remember that I took to get here are:
1. Installed driver for jlink edu mini
2. Ran jlink.exe, it prompted me to update firmware, which I did.
3. Ran USB Driver Tool to set at WinUSB
4. Ran OpenOCD (see below)

I found on the web that someone else mentioned issues with jlink edu mini, so I'm wondering if it works? And if not, why doesn't it work, like who should I follow up with next?

Here's the log output

Code: Select all

PS> openocd -f interface/jlink.cfg -f board/esp-wroom-32.cfg
Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
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
Warn : Failed to receive data from device: LIBUSB_ERROR_TIMEOUT.
Info : J-Link EDU Mini V1 compiled Oct 22 2019 16:28:45
Warn : Failed to receive data from device: LIBUSB_ERROR_TIMEOUT.
Info : Hardware version: 1.00
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_get_hardware_status() failed: timeout occurred.

Warn : Flash driver of esp32.flash does not support free_driver_priv()
Warn : Flash driver of irom does not support free_driver_priv()
Warn : Flash driver of drom does not support free_driver_priv()
Thanks -Paul

PaulELong
Posts: 14
Joined: Thu Oct 24, 2019 9:47 pm

Re: Help debugging ESP32 WROOM with jlink edu mini

Postby PaulELong » Tue Nov 19, 2019 10:03 pm

I determined I made a stupid mistake, though debugging with jlink edu mini is not working yet. The first problem is that I had the cable backwards. I picture I found showed it connected incorrectly which I now found is backwards. I see that it connects, but now it's getting timeout errors. I do see another similar complaint with no solution, so perhaps OpenOCD doens't support the jlink edu mini.

If somebody has this working, I would like to hear about it.

This is my log now

Code: Select all

PS> openocd -f interface/jlink.cfg -f board/esp-wroom-32.cfg
Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 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 : J-Link EDU Mini V1 compiled Oct 22 2019 16:28:45
Info : Hardware version: 1.00
Info : VTarget = 3.292 V
Info : clock speed 1000 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 : Detected debug stubs @ 3ffb2980 on core0 of target 'esp32'
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
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!
...

Who is online

Users browsing this forum: ESP_Sprite and 101 guests