TracesOfNut

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: using rpi as ftag debugger for esp32 #20907
    TracesOfNut
    Participant

    HI,

    I tried following the suggested article and this time I had different problems. Previously I had done the same thing following a similar article and the ESp32 was being recognised ok by the openocd on the raspberry pi.  This time, I am getting a different error which I forgot to write down.

    Unfortunately I have had to stop trying for a short time due to work.  I will try again in a few days and report back.

    regards

    Justin.

    in reply to: using rpi as ftag debugger for esp32 #20878
    TracesOfNut
    Participant

    This morning, I decided to buy a proper debugger, but the raspberry pi is still something I would like solve eventually.

    With custom gdb mode, i couldn’t find where to enter in the target remote command.  I tried the -interpreter mi argument though with both options without success.

    With the gdb devices, this ( see below )  is what gets reported under windows when I tried the sysfsgpio-raspberrypi interface (The command is basically the same as the one I run on the raspberry pi).  I noticed when I build openocd, I have to use the –enable_sysfsgpio for make as it is not preselected.  There was another device in the VisualGDB list, but I was trying random ones to see if any expected a network address, and can’t remember which one.

    With VisualGDB, I am assuming that the openocd running on the PI is basically acting as a GDB server.  I can understand why that one needs the sysfsgpio-raspberrypi.cfg interface configuration in order to communicate through the gpio pins, but why does the openocd running under VisualGDB (windows 10) need to know about it?

    Justin.

    c:\SysGCC\esp32\esp32-bsp\OpenOCD\bin\openocd.exe -c “gdb_port 57902” -c “telnet_port 57903” -f interface/sysfsgpio-raspberrypi.cfg -f target/esp32.cfg -c “adapter_khz 3000” -c “echo VisualGDB_OpenOCD_Ready”
    Open On-Chip Debugger 0.9.0 (2017-08-05)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    Error: The specified debug interface was not found (sysfsgpio)
    The following debug interfaces are available:
    1: ft2232
    2: ftdi
    3: usb_blaster
    4: usbprog
    5: jlink
    6: vsllink
    7: rlink
    8: ulink
    9: arm-jtag-ew
    10: hla
    11: osbdm
    12: opendous
    13: aice
    14: cmsis-dap

     

Viewing 2 posts - 1 through 2 (of 2 total)