microsoft / microsoft/vscode-cpptools

Support restart debugging embedded targets (with custom commands)

Open
#10,558 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger embedded
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Feature Request

To debug an embedded target using a SEGGER J-Link I followed #9956.
Debugging works fine. But the restart button does just stop the debugging.

Currently I'm using cortex-debug and there it is possible to overwrite commands as described here.

...
            "overrideLaunchCommands": [
                "monitor halt",
                "monitor reset",
                "-target-download",
                "monitor reset"
            ],
            "overrideResetCommands": [
                "monitor reset",
            ],
            "overrideRestartCommands": [
                "monitor reset",
            ]
...

Which then allows to restart the debugging with the built-in buttons.
image

Is there a similar thing already present? Or could this be added in the future?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the debugging setup from issue #9956 and the restart behavior in the C/C++ extension, then compare it with the cortex-debug command overrides shown here. Done means embedded targets can use custom launch, reset, and restart commands through the built-in debugging controls.

Written by the indexing model from the issue text.

Assessment

Domain
devtools, embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.