I saw your note about openocd version after my last update. I have now updated openocd to v0.10.0-esp32-20200420 which seems to be much more successful, at least at 500 KHz. There were a couple of intermediate versions of openocd in my "dist" folder but it is not obvious on how to update the version...

I Went up a couple of wire sizes to ensure solid connections, I am running at 500 KHz for JTAG Speed. I am now back to using the solo-1 configuration file for openocd. Overriding SPI voltage to 3.3. One of the other postings indicated that -c "gdb_breakpoint_override hard" might help. I am still get...

I have dropped the JTAG speed to 500k, If you have information that lower speeds are appropriate, please let me know what can be expected to work.

This is a repeating issue - Debug: 13978 17959 esp32.c:2163 xtensa_esp32_examine(): xtensa_esp32_examine: Target idcode=0733bff2 DSR=8000cc11 Debug: 13979 17959 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_esp32 invoke-event examine-end Debug: 13980 17959 command.c:143 sc...

or this case, where it connects to GDB and then goes into an error state 11727 11758 core.c:1521 jtag_init_reset(): Initializing with hard TRST+SRST reset Debug: 11728 11758 core.c:742 jtag_add_reset(): JTAG reset with TLR instead of TRST Debug: 11729 11758 core.c:327 jtag_call_event_callbacks(): jt...

Than you for a response, in that case, how do you explain Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1) Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates target still busy! Error: cpu0: xtensa_write_memory (line 802): DS...

I have a fault I cannot understand. One one of my ESP32-U4WDH devices on Modified Solo-1 DevKitC Modules, I cannot connect to JTAG. The statements highlighted below seem to be the cause. My other two devices respond and I get Info : 394 874 core.c:959 jtag_examine_chain_display(): JTAG tap: esp32.cp...

It does look like you are a couple versions out of date on the esptool.

I have not taken a close enough look at this device to be sure but I expect you are feeding the internal GPIO resisters among other things. I would try making all the GPIOs you are not using inputs without any pull-up/down features enabled. I know that I was able to reduce my average current on a AR...

you need a line like

adapter_khz 1000

in your board description file