Skip to main content
Associate
May 29, 2025
Solved

STM32cube registers tree cannot close when debug complete

  • May 29, 2025
  • 2 replies
  • 704 views

sukiElaina_0-1748499764542.png

Each time the debug function is used, there will be one more item in the STM32cube registers tree of the debug interface

Best answer by Cartu38 OpenDev

Known behavior ...
https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32cube-ide-registers is claiming to inherit from https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.peripheral-inspector and this one behaves the same.
Very same applies to https://marketplace.visualstudio.com/items?itemName=mcu-debug.peripheral-viewer

Sounds kind of must have if running multiple debug sessions at same time (multi core devices as example) but for basic device a bit annoying yes.
Workaround I've found is to reload or restart VSCode

Cartu38OpenDev_0-1748527345635.png

 

2 replies

ST Employee
May 29, 2025

Hello @sukiElaina,

Could you share your debug configuration in launch.json? 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate
May 29, 2025
{
            "type": "stlinkgdbtarget",
            "request": "launch",
            "name": "STM32Cube: STM32 Launch ST-Link GDB Server",
            "origin": "snippet",
            "cwd": "${workspaceFolder}",
            "runEntry": "main",
            "imagesAndSymbols": [
                {
                    "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}"
                }
            ],
            "preBuild": "${command:st-stm32-ide-debug-launch.build}"
        }
sukiElaina_0-1748527541601.png

 

Cartu38 OpenDev
Graduate II
May 29, 2025

Known behavior ...
https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32cube-ide-registers is claiming to inherit from https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.peripheral-inspector and this one behaves the same.
Very same applies to https://marketplace.visualstudio.com/items?itemName=mcu-debug.peripheral-viewer

Sounds kind of must have if running multiple debug sessions at same time (multi core devices as example) but for basic device a bit annoying yes.
Workaround I've found is to reload or restart VSCode

Cartu38OpenDev_0-1748527345635.png