2025-12-10 12:58 AM
I wanted to inspect the memory using the built-in Memory View window in VS Code, but the option is unavailable even though the debugging is on at that time, and it says "Add a new view using the plus button in the Toolbar with the debugger paused. Supported debuggers: cspy, cortex-debug, cppdbg."
Is this a limitation of the current ST-Link GDB debugger in STM32 VS Code extension version?
2025-12-10 12:57 PM
@rowellsa
You're not relying on proper memory view.
Right one is :
You're on :
Let's check CDT one is installed and call it Thanks (takes care this view is only available having a debug session active)
2025-12-10 12:59 PM
Has to look like
2025-12-10 4:50 PM
Isn't this curious that a viewer for Eclipse CDT (CubeIDE) works with Code, and one for mcu-debug does not?
2025-12-10 9:05 PM
No magic answer is here I guess : https://github.com/mcu-debug/memview/blob/f9cb7f463d079b808f642bf553135bcba7addcc4/package.json#L34
2025-12-10 9:46 PM
Are you able to Memory view in Cube IDE?
2025-12-10 10:30 PM
@MGogr.1 not sure to understand your question here. Yes i'm able relying on CDT extension. I've shared snapshot of view running above.