A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/espressif/openocd-esp32/issues/367 below:

esp32.tap1 on esp32-solo-1 (OCD-1215) · Issue #367 · espressif/openocd-esp32 · GitHub

Development Kit

Custom Board

Module or chip used

ESP-SOLO-1

Debug Adapter

ESP-PROG

OpenOCD version

v0.12.0-esp32-20250422

Operating System

Windows 11

Using an IDE ?

VS code

OpenOCD command line

openocd -l openocd_log.txt -d3 -f interface/ftdi/esp_ftdi.cfg -f target/esp32-solo-1.cfg

JTAG Clock Speed

20000 kHz

ESP-IDF version

v5.4.2

Problem Description

I'm having trouble getting JTAG to connect to an ESP32-Solo-1. I had this working a couple of years ago (around 2–3 years back), but I can't seem to find the correct settings to get it working again.

From the output console, it looks like it's still trying to connect to a second core, even though my settings.json file specifies the target as "target/esp32-solo-1.cfg". The application runs fine when uploaded over UART, so I believe the menu configuration is correct (unicore is enabled).

openocd -l openocd_log.txt -d3 -f interface/ftdi/esp_ftdi.cfg -f target/esp32-solo-1.cfg :
openocd_log.txt

openocd -f interface/ftdi/esp32_devkitj_v1.cfg -f target/esp32-solo-1.cfg -l openocd_devkitj.txt -d3 :
openocd_devkitj.txt

Debug Logs Expected behavior

OpenOCD to connect to the board.

Screenshots

No response

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4