Description
It is often expected that debug views in an embedded debugger allow target interaction with a Cortex-M CPU while running.
In CMSIS Debugger for VS Code this depends on a couple of parameters: used debugger backend, VS Code built-in views vs view extensions, involved description engines.
We need to review current documentation and be more specific about the debugger capabilities while a CPU is running to set expectations right.
Starting points for the docs
Views that allow read/edit while running with pyOCD and J-Link today:
- Memory Inspector
- Peripheral Inspector
Views that allow reading while running, and where editing while running is under investigation
Views that allow reading while running, but not editing while running
- Component Viewer
- Core Peripherals
Views that allow neither read nor edit while running due to the lack of support in VS Code:
- Call Stack
- Variables
- Watch
Is this request a Security Requirement?
Priority
Medium
Related Issues (Optional)
No response
Additional Notes (Optional)
No response
Description
It is often expected that debug views in an embedded debugger allow target interaction with a Cortex-M CPU while running.
In CMSIS Debugger for VS Code this depends on a couple of parameters: used debugger backend, VS Code built-in views vs view extensions, involved description engines.
We need to review current documentation and be more specific about the debugger capabilities while a CPU is running to set expectations right.
Starting points for the docs
Views that allow read/edit while running with pyOCD and J-Link today:
Views that allow reading while running, and where editing while running is under investigation
Views that allow reading while running, but not editing while running
Views that allow neither read nor edit while running due to the lack of support in VS Code:
Is this request a Security Requirement?
Priority
Medium
Related Issues (Optional)
No response
Additional Notes (Optional)
No response