ESP32 Forum

Posted: **Thu Sep 30, 2021 10:09 pm**

Hello,

I am using ESP32 S2 Kaluga-1 dev kit and I am trying to get the debugger working . But When I run the Open OCD I see the error below

Code: Select all

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 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: esp32s2.cpu: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

I tried both in MAC and Windows . I am using Windows 10 and MAC Bigsur.

I tried to replace the FTDI driver with Windows using Zadig on Windows . Still I dont see any changes. I am stuck . Any help appreciated .

Thanks

Posted: **Fri Oct 01, 2021 5:19 pm**

pranathi wrote: ↑
Thu Sep 30, 2021 10:09 pm
I am using ESP32 S2 Kaluga-1 dev kit

hi
how looks your code?
Perhaps you are using IO12-IO15 for something else?

edit: Kaluga S2 i did overread in first step..,
wich Kit Version you use?
Getting started..

Shematic, related Documents

JTAG Switch
Switch to ON to enable connection between ESP32-S2 and FT2232; JTAG debugging will then be possible using USB-UART/JTAG Port.
See also JTAG Debugging.

USB-UART/JTAG Port
Communication interface (UART or JTAG) between a PC and the ESP32-S2 module.

does it help?
- Configure ESP32-S2- Kaluga
- JTAG Debugging

If the ESP32-S2-Kaluga-1 is used, then connection from PC to ESP32-S2 is done effectively with a single USB cable. This is made possible by the FT2232H chip, which provides two USB channels, one for JTAG and the other for UART connection.

- Selecting JTAG Debugger

best wishes
rudi

ESP32 Forum

ESP32 S2 Kaluga does not connect to debugger

ESP32 S2 Kaluga does not connect to debugger

Re: ESP32 S2 Kaluga does not connect to debugger