Skip to main content
Visitor II
December 10, 2025
Question

About Memory View for Debugging With STM32 VS Code

  • December 10, 2025
  • 3 replies
  • 167 views

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?

    This topic has been closed for replies.

    3 replies

    Graduate II
    December 10, 2025

    @rowellsa 
    You're not relying on proper memory view.
    Right one is :

    Cartu38OpenDev_0-1765400099601.png
    You're on :

    Cartu38OpenDev_1-1765400139000.png


    Let's check CDT one is installed and call it Thanks (takes care this view is only available having a debug session active)
    Cartu38OpenDev_2-1765400243241.png

     

    Graduate II
    December 10, 2025

    Has to look like

    Cartu38OpenDev_3-1765400335739.png

     

    Super User
    December 11, 2025

    Isn't this curious that a viewer for Eclipse CDT (CubeIDE) works with Code, and one for mcu-debug does not? 

    Graduate II
    December 11, 2025
    Explorer
    December 11, 2025

    Are you able to Memory view in Cube IDE?

    Graduate II
    December 11, 2025

    @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.