As a parting note I also had a problem with the error message: Error: esp32: Failed to read insn (-4)! Error: esp32: Failed to add SW BP! Error: can't add breakpoint: resource not available I was able to fix this by adding -c "gdb_breakpoint_override hard" to the openocd command line: bin/openocd -c...

So I wiped out my esp-idf, toolchain, openocd, and example code and started over, and it works now. I thought I had the latest, but something must have been out of sync. Thanks for the help.

Will do, thanks.

Looks like the same problem. Is the devkitj interface the right one to use? I'm using the esp-prog with only the 4 jtag lines, ground, and Vjtag connected. openocd window user1@NUCi7Linux ~/esp/openocd-esp32 $ bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-w...

Folks, I'm having trouble debugging using esp-prog, and an esp32_core_board on linux. when I run openocd (prebuilt), I get: user1@NUCi7Linux ~/esp/openocd-esp32 $ bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg Open On-Chip Debugger v0.10.0-esp32...

So I discovered that holding down the boot button fixes the problem in this configuration (linux VM on Windows). This isn't required for running natively in Windows.

Is this an inherent limitation of running in the VM?

Folks, I'm having trouble programming a devkit c v4 (and another board) using a virtualbox running Linux Mint (latest version) guest on a Windows 10 host. I added the user to the dialout group. I captured the "Silicon Labs CP2012N USB to UART bridge controller" usb driver to the virtualbox. The corr...