Remote debugging still expects local probe

Sysprogs forums Forums VisualGDB Remote debugging still expects local probe

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

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

    davidoz
    Participant

    Hi All,

    I’m debugging remotely.  The remote pc is running openocd and has an st-link probe connected to the board.  My host pc is running VisualGDB.  The remote debugging works, except VisualGDB also expects an st-link probe to be attached locally.

    Is there a way of telling VisualGDB that it should not start openocd locally and connect to the st-link.  A redacted screenshot is attached.

    Cheers

    David

     

    Attachments:
    You must be logged in to view attached files.
    #32659

    support
    Keymaster

    Hi,

    The regular OpenOCD GUI is indeed optimized for running OpenOCD locally – it can automatically find the supported JTAG/SWD probes, install drivers, locate device scripts, etc.

    If you would like to run OpenOCD remotely, please try selecting the “Full-custom” debug method instead of OpenOCD. It allows specifying arbitrary target connection commands, and will not attempt to do anything beyond what is explicitly configured.

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

You must be logged in to reply to this topic.