Forum Replies Created
yes I did.
In the meantime I found out what causes my issue:
- I forgot a decoupling cap at the ESP32 3.3V pin.
- The JTAG mini 10 pole cable/connector is a little bit unstable it seems.
Now, sometimes the upload works, sometimes it does not. Not sure if OpenGDB combined with a non natively supported J-Link also add to this unstable behavior.
- This reply was modified 1 year ago by esp32dude.
J-Link works with dev boards like ESP32-WROVER.
The issue is, I have a custom board and only have the JTAG interface. Maybe you can have a look at the ESP32 schematic if you see any issue?
- This reply was modified 1 year, 1 month ago by esp32dude.
I was following this tutorial: https://visualgdb.com/tutorials/esp32/wroom/
There it was suggested to use Embedded wizard.
Anyways, for ESP-IDF wizard, I cannot connect to ESP32 over J-Link. I checked the pinning, it is correct.
Here is the error log:
C:\Users\XXXXX\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 50443” -c “telnet_port 50444” -f interface/jlink.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2019-10-24)
Licensed under GNU GPL v2
For bug reports, read
adapter speed: 3000 kHz
Info : Configured 2 cores
Info : Listening on port 6666 for tcl connections
Info : Listening on port 50444 for telnet connections
Error: type ‘esp32’ is missing virt2phys
Warn : Failed to open device: LIBUSB_ERROR_NOT_SUPPORTED.
Info : J-Link V11 compiled Aug 14 2019 16:21:09
Info : Hardware version: 11.00
Info : VTarget = 0.000 V
Info : clock speed 3000 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 50443 for gdb connections
Info : accepting ‘gdb’ connection on tcp/50443
Error: No symbols for FreeRTOS
Error: Target not examined yet
Error: Target not halted
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use ‘gdb_memory_map disable’.
Error: attempted ‘gdb’ connection rejected