I’ve been using VisualGDB to successfully JTAG debug all of the currently-supported ESP-IDF v5.1 targets with the exception of the ESP32-H2.
I see in this thread that the ESP32H2 was supported in VisualGDB starting with EDP-IDF v5.0.
I’ve tried this on two different, genuine Espressif ESP32-H2 dev kits: one that I bought from Mouser last summer and most recently this ESP32-H2-DevKitM-1-N4 from Amazon.
When I press the “test” button on the “Debug Settings” of the “VisualGDB Project Properties”, the device is immediately found, but then gets stuck after “Warn : No symbols for FreeRTOS!” (see attached log file).
I’ve tried various speed settings, different cables, different Windows drivers (via Zadig), I even tried hooking up my known-to-work Tigard JTAG board that curiously encountered the same problem.
I’m not sure if this is a VisualGDB issue or perhaps something unusual with the ESP32-H2 USB port.
Has anyone been able to single-step code on an ESP32-H2?
I’m using Visual Studio Enterprise 2022 17.7.6 and VisualGDB 5.6. Here is the VisualGDB project file that I’m using.
It really looks like something between the Espressif’s OpenOCD port and the chip. We are not affiliated with Espressif and do not have insights into their chips or tools beyond their official documentation.
If you suspect VisualGDB is using OpenOCD incorrectly, you can always try running the binaries from Espressif manually. If they also don’t work, please contact Espressif for further help. If they do work, please try comparing the command lines between the working and broken setup. If you can point out a specific difference causing the issue, we can gladly investigate it further.
That said, we have recently updated our OpenOCD package to match the latest release from Espressif. Please try installing it via VisualGDB Package Manager. It may contain a fix for this specific issue.