Steps I followed :
> Changed the J-link driver with WinUSB driver
> Debug Settings in Visual GDB :
Debug using : Open OCD
JTAG/SWD Programmer : Segger J-link
Target device : ESP32
Program FLASH Memory : Always
- Debug using : Open OCD
- JTAG/SWD Programmer : Segger J-link
- Target device : ESP32
- Program FLASH Memory : Always
- Program FLASH using : OpenOCD(via J-TAG)
connector used : https://www.segger.com/products/debug-p ... m-adapter/
J-link - ESP32 connections
- (1)VTREF - 3V3
- (Pin 5)TDI - MTDI(IO12)
- (Pin 7)TMS - MTMS(IO14)
- (Pin 9)TCK - MTCK(IO13)
- (Pin 13)TDO - MTDO(IO15)
- (Pin 15)RESET - EN(3) Pin
Meanwhile when I tried same thing with my ESP32 DEVKITC, I have only replaced Reset pin of the controller to 3rd pin of J-LINK i.e. nTRST in that case I am able to debug my development board but when I am trying to debug using the above given connections I am not able to debug my device. Also 24-10 pin converter has RESET pin is connected to 15th pin of J-LINK.
1. What is difference between nTRST and RESET pin in J-LINK while debugging ESP32 ?
2. What is Ideal method to debug ESP32 while using Visual Studio w/ Visual GDB ?