ESP32-Pico-V3 fails to upload/debug using esp-prog

maxgerhardt · October 26, 2020, 10:14am

It’s still running at 20MHz, I think you have to change this in that file

espressif/openocd-esp32/blob/master/tcl/interface/ftdi/esp32_devkitj_v1.cfg#L36


      
          # SPDX-License-Identifier: GPL-2.0-or-later
          #
          # Driver for the FT2232H JTAG chip on the Espressif DevkitJ board
          # (and most other FT2232H and FT232H based boards)
          #
          
          adapter driver ftdi
          ftdi vid_pid 0x0403 0x6010 0x0403 0x6014
          
          # interface 1 is the uart
          ftdi channel 0
          
          # TCK, TDI, TDO, TMS: ADBUS0-3
          # LEDs: ACBUS4-7
          
          ftdi layout_init 0x0008 0xf00b
          ftdi layout_signal LED -data 0x1000
          ftdi layout_signal LED2 -data 0x2000
          ftdi layout_signal LED3 -data 0x4000
          ftdi layout_signal LED4 -data 0x8000
          
          # ESP32 series chips do not have a TRST input, and the SRST line is connected to the EN pin.
          # The target code doesn't handle SRST reset properly yet, so this is commented out:
          # ftdi layout_signal nSRST -oe 0x0020
          # reset_config srst_only
          
          # The speed of the JTAG interface, in kHz. If you get DSR/DIR errors (and they
          # do not relate to OpenOCD trying to read from a memory range without physical
          # memory being present there), you can try lowering this.
          #
          # On DevKit-J, this can go as high as 20MHz if CPU frequency is 80MHz, or 26MHz
          # if CPU frequency is 160MHz or 240MHz.
          adapter speed 20000

(That also helped for a PICO-D4 according to an issue)

Since this issue seems to be actually new and unrelated to all other posts that was indeed the right thing to do.

Now the question here is if even the latest released esp32 openocd version from July 2020 is too old. Since I don’t have a Mac, I’m unable to compile the most recent version, and I also can’t seem to find officially released packages which are newer (or I have overlooked them).

Now to test this either someone can build for Mac or I’m building it for Linux and the thing has to be tested in a Linux VM with the USB debugger passed-through.