I want install openocd enable Segger Jlink, after make install Openocd, there esp32.cfg(/usr/local/share/openocd/target/esp32.cfg) have not the "source [find interface/ftdi/tumpa.cfg]",
The origin souce code directory folder have not this line also, please have a look.
Does the config file upgrade. but Doc not?
esp32.cfg have no "source [find interface/ftdi/tumpa.cfg]" line, for Openocd debugging
Re: esp32.cfg have no "source [find interface/ftdi/tumpa.cfg]" line, for Openocd debugging
Hi wziy520,
openocd separates the idea of an "interface" from a "target". TUMPA in this case is a type of interface (based around an FTDI chip) J-Link is a different type of interface. ESP32 is the target.
I think at one point tumpa.cfg was included from esp32.cfg, but this prevents you using other interfaces (like your J-Link) with the ESP32.
For Segger JLink, the command line will be something like this:
I don't jave a J-Link to test with, there may be additional interface-specific configuration commands required between these two.
Angus
openocd separates the idea of an "interface" from a "target". TUMPA in this case is a type of interface (based around an FTDI chip) J-Link is a different type of interface. ESP32 is the target.
I think at one point tumpa.cfg was included from esp32.cfg, but this prevents you using other interfaces (like your J-Link) with the ESP32.
For Segger JLink, the command line will be something like this:
Code: Select all
openocd -f interface/jlink.cfg -f target/esp32.cfg
Angus
Who is online
Users browsing this forum: Baidu [Spider] and 108 guests