How to JTAG debugging multiple ESP32-WROVER Board.

Sysprogs forums Forums VisualGDB How to JTAG debugging multiple ESP32-WROVER Board.

This topic contains 1 reply, has 2 voices, and was last updated by  support 1 week, 2 days ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #23323

    kevinn
    Participant

    Hi,

    I need to JTAG debugging two ESP32-WROVER board on the same computer.

    But, it seems that VisualGDB OpenOCD always select the same board.

    My question is how to configure VisualGDB to specify a speect ESP32-WROVER board to use?

    Thanks,

     

    Test Log below:

    Open On-Chip Debugger 0.9.0 (2018-10-12)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    none separate
    adapter speed: 3000 kHz
    Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
    esp32 interrupt mask on
    VisualGDB_OpenOCD_Ready
    Info : clock speed 3000 kHz
    Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
    Info : Target halted. PRO_CPU: PC=0x401354DE (active) APP_CPU: PC=0x401354DE
    Info : Detected debug stubs @ 3ffb34e0 on core0 of target ‘esp32’
    cpu0: Current bits set: BreakIn BreakOut RunStallIn
    cpu1: Current bits set: BreakIn BreakOut RunStallIn
    Info : accepting ‘gdb’ connection on tcp/2995
    Info : Target halted. PRO_CPU: PC=0x4009170E (active) APP_CPU: PC=0x401354DE
    Info : Flash mapping 0: 0x1 -> 0xfffffd01, 2097711 KB
    Info : Flash mapping 1: 0x3ffc0610 -> 0x0, 0 KB
    Info : Target halted. PRO_CPU: PC=0x4009170E (active) APP_CPU: PC=0x401354DE
    Info : Auto-detected flash size 4096 KB
    Info : Using flash size 4096 KB
    Info : Target halted. PRO_CPU: PC=0x4009170E (active) APP_CPU: PC=0x401354DE
    Info : Flash mapping 0: 0x1 -> 0xfffffd01, 2097711 KB
    Info : Flash mapping 1: 0x3ffc0610 -> 0x0, 0 KB
    Info : Using flash size 0 KB
    Info : Target halted. PRO_CPU: PC=0x4009170E (active) APP_CPU: PC=0x401354DE
    Info : Flash mapping 0: 0x1 -> 0xfffffd01, 2097711 KB
    Info : Flash mapping 1: 0x3ffc0610 -> 0x0, 0 KB
    Info : Using flash size 0 KB
    Info : dropped ‘gdb’ connection
    Info : Restore debug stubs @ 3ffb34e0 on core0 of target ‘esp32’

     

    #23326

    support
    Keymaster

    Hi,

    Please try creating a temporary copy of the interface configuration file (e.g. esp32_devkitj_v1.cfg) and add the ftdi_serial command there (OpenOCD should show the serial numbers of connected devices if multiple matching adapters are found), then specify the copied script in the Debug Settings.

    Normally VisualGDB should do this automatically, however we have not explicitly tested this with the ESP32 devices, so minor adjustments might be required. Feel free to let us know your observations and we should be able to update VisualGDB to do this automatically.

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

You must be logged in to reply to this topic.