Issue while debuggging ESP32-S3 using J-Link
Posted: Fri May 27, 2022 9:20 am
Hello,
I am trying to debug my ESP32-S3 in DevkitC using J-link. but I am not able to connect the way I am used to do in ESP32-WROOM32E.
I reffered the IO connections as per the data provided here: https://docs.espressif.com/projects/esp ... itc-1.html
I am using Visual Studio with Visual GDB extension.
Debug settings for ESP32 is shown in attachments
Error message shown :
I am trying to debug my ESP32-S3 in DevkitC using J-link. but I am not able to connect the way I am used to do in ESP32-WROOM32E.
I reffered the IO connections as per the data provided here: https://docs.espressif.com/projects/esp ... itc-1.html
I am using Visual Studio with Visual GDB extension.
Debug settings for ESP32 is shown in attachments
- Debug settings for ESP32-S3
- dbg_setting.PNG (52.87 KiB) Viewed 2724 times
C:\Users\APRASAD\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c "gdb_port 64550" -c "telnet_port 64548" -f interface/jlink.cfg -c "adapter_khz 3000" -f target/esp32s3.cfg -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.10.0 (2022-05-03)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter speed' not 'adapter_khz'
adapter speed: 3000 kHz
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 64548 for telnet connections
Info : J-Link V9 compiled May 7 2021 16:26:12
Info : Hardware version: 9.30
Info : VTarget = 3.282 V
Info : clock speed 3000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32s3.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : target esp32s3.cpu0 examination failed
Warn : target esp32s3.cpu1 examination failed
Info : starting gdb server for esp32s3.cpu0 on 64550
Info : Listening on port 64550 for gdb connections
Info : accepting 'gdb' connection on tcp/64550
Error: Target not examined yet
Error executing event gdb-attach on target esp32s3.cpu0:
Warn : No symbols for FreeRTOS!
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