Well I can only think of a few more things:
- When modifying the adapter speed make sure to modify the
esp32-wrover.cfg
, the linked topic refers to a different file because it has a different target board - In the
esp32-wrover.cfg
, there are settings for the target flash voltage (either 1.8V or 3.3V). If I read openocd-esp32/esp32-ethernet-kit-3.3v.cfg at master · espressif/openocd-esp32 · GitHub correctly, this board needs the 3.3V config. Make sure the file is configured as in JTAG-Debugging with ESP32-WROOM-32UE - #4 by maxgerhardt. - Re-Check all wires for good continuity and shortness, or replace them with new ones. Usually reading only 1’s (as in
0xFFFFFFFF
) on a JTAG line indicates a bad connection (or too high adapter speed) - It might just be that the
tool-openocd-esp32
needs an update (latest files found in GitHub - espressif/openocd-esp32: OpenOCD branch with ESP32 JTAG support). For a test, these files can be locally replaced (inC:\Users\<user>\packages\tool-openocd-esp32
. Then one can also directly make use of the new openocd config for the board by usingboard_debug.openocd_board = esp32-ethernet-kit-3.3v.cfg
in theplatformio.ini
. But let’s try the above things first.