-
Notifications
You must be signed in to change notification settings - Fork 150
Description
Environment
Not relevant but
Development Kit: ESP32-C3 mini devkit
Module or chip used: ESP32-C3 mini
Debug Adapter: Built in
OpenOCD version: (trying to build)
Operating System: Windows 10
Other things not relevant
ESP-IDF version: Master Branch
Problem Description
Steps to reproduce the behavior:
I created this issue report:
#158 I am trying to evaluate the ESP32-C3 mini devkit.
I cannot get JTAG debugging to work. Since issue 158 was closed it seems reasonable that I should be trying with the most recent OpenOCD for ESP32. I cannot find a binary so I figured I would try and build it using MSYS2 following these instructions https://docs.espressif.com/projects/esp-idf/en/v3.3.4/api-guides/jtag-debugging/building-openocd-windows.html.
After ./configure I get this configuration summary
OpenOCD configuration summary
MPSSE mode of FTDI based devices no
cJTAG OSCAN1 tunneled thru MPSSE no
ST-Link Programmer no
TI ICDI JTAG Programmer no
Keil ULINK JTAG Programmer no
Altera USB-Blaster II Compatible no
Bitbang mode of FT232R based devices no
Versaloon-Link JTAG Programmer no
TI XDS110 Debug Probe no
OSBDM (JTAG only) Programmer no
eStick/opendous JTAG Programmer no
Espressif JTAG Programmer no
Andes JTAG Programmer no
USBProg JTAG Programmer no
Raisonance RLink JTAG Programmer no
Olimex ARM-JTAG-EW Programmer no
CMSIS-DAP Compliant Debugger no
Cypress KitProg Programmer no
Altera USB-Blaster Compatible no
ASIX Presto Adapter no
OpenJTAG Adapter no
SEGGER J-Link Programmer yes (auto)
Note that espressif is no.
According to the documentation
"If the information of your device is not shown in the log, use ./configure to enable it as described in ../openocd-esp32/doc/INSTALL.txt."
There is no INSTALL.txt file in the source tree. Online searches yield references to INSTALL.txt but not the relevant file.
When I make I get numerous errors such as
In file included from src/jtag/drivers/libusb_common.h:24,
from src/jtag/drivers/jtag_esp_remote.c:38:
src/jtag/drivers/libusb0_common.h:26:36: error: unknown type name 'usb_dev_handle'
26 | #define jtag_libusb_device_handle usb_dev_handle
| ^~~~~~~~~~~~~~
These may or may not be because the INSTALL.txt file is missing.
Expected behavior
I would expect make to result in an executable.
Since my objective is to test the devkit, ideally I would like an updated Windows executable but failing that instructions for successful configuration and build on Windows/MSYS2. Regardless, the build instructions should match the build process.