bound doStepSettingsValidation Failed: Device not found: Error: Missing CMSIS_PACK_ROOT

[Jmace]

Hello,

I'm trying to get familiar with the STM32Cube extension for VSCode.
I generated a basic STM32 project using STM32CubeMX, for my NUCLEO-H723ZG board.

I then imported the generated cmake project using the extension tool, and configured it using the "setup STM32Cube project(s)" button of the extension, which created a launch.json file.

When I try to run the debug config, I get the following error : bound doStepSettingsValidation Failed: Device not found: Error: Missing CMSIS_PACK_ROOT

Here is the STM32Cube core output :

025-10-20 16:19:33.002 [Info] Adding STM32Cube CLI path to environment: c:\Users\Jacques\.vscode\extensions\stmicroelectronics.stm32cube-ide-core-1.0.3\resources\binaries\win32\x86_64
2025-10-20 16:19:33.057 [Info] Configuring CMSIS_PACK_ROOT environment: C:\Users\Jacques\AppData\Local\stm32cube\packs
2025-10-20 16:19:33.099 [Info] Configuring CUBE_BUNDLE_PATH environment: C:\Users\Jacques\AppData\Local\stm32cube\bundles
2025-10-20 16:19:33.805 [Info] cube wrapper version: 0.8.3
2025-10-20 16:19:33.816 [Info] Installing STM32Cube bundles prerequisites
2025-10-20 16:19:34.090 [Info] Syncing CMSIS-Pack metadata for C:\Users\Jacques\AppData\Local\stm32cube\packs
2025-10-20 16:19:34.091 [Info] NODE_EXTRA_CA_CERTS=undefined
2025-10-20 16:19:34.093 [Info] STM32Cube Core activated in 1113ms
2025-10-20 16:19:34.095 [Info] No need to sync metadata, since recently updated.
2025-10-20 16:19:34.442 [Info] Online bundle cache built

It seems the CMSIS_PACK_ROOT variable is indeed created.

I already read this thread : https://community.st.com/t5/stm32cubeide-for-visual-studio/missing-cmsis-pack-root/td-p/804489
It did not help me solve the issue.

Do you guys have any idea how to solve the issue ?

Thanks for your help

[Julien D]

Hello @Jmace,

This is unfortunately an old story that we are still unable to reproduce.

Do you have a lot of VSCode extensions installed in the default profile?

If so could you maybe try to create a separated VSCode profile with only "STM32CubeIDE for VSCode" extensions pack installed, and check if it works better?

[Jmace]

Hello @Julien D ,

Thanks for your prompt answer.

I indeed had a lots of extensions on my main profile.

Creating a dedicated profile with only the STM32Cube extensions fixed the issue!

FYI, here are the extensions installed on my main profile :

PS E:\Projets\STM32\workspace\nucleo-h7-vscode-test> code --list-extensions
angular.ng-template
continue.continue
denoland.vscode-deno
docker.docker
eclipse-cdt.memory-inspector
eclipse-cdt.serial-monitor
espressif.esp-idf-extension
marlinfirmware.auto-build
ms-azuretools.vscode-containers
ms-azuretools.vscode-docker
ms-python.debugpy
ms-python.python
ms-python.vscode-pylance
ms-python.vscode-python-envs
ms-vscode-remote.remote-containers
ms-vscode-remote.remote-ssh
ms-vscode-remote.remote-ssh-edit
ms-vscode-remote.remote-wsl
ms-vscode.cmake-tools
ms-vscode.cpptools
ms-vscode.cpptools-extension-pack
ms-vscode.cpptools-themes
ms-vscode.makefile-tools
ms-vscode.remote-explorer
ms-vscode.vscode-typescript-next
platformio.platformio-ide
prisma.prisma
ritwickdey.liveserver
rust-lang.rust-analyzer
stmicroelectronics.stm32-vscode-extension
stmicroelectronics.stm32cube-ide-build-analyzer
stmicroelectronics.stm32cube-ide-build-cmake
stmicroelectronics.stm32cube-ide-bundles-manager
stmicroelectronics.stm32cube-ide-clangd
stmicroelectronics.stm32cube-ide-core
stmicroelectronics.stm32cube-ide-debug-core
stmicroelectronics.stm32cube-ide-debug-generic-gdbserver
stmicroelectronics.stm32cube-ide-debug-jlink-gdbserver
stmicroelectronics.stm32cube-ide-debug-stlink-gdbserver
stmicroelectronics.stm32cube-ide-project-manager
stmicroelectronics.stm32cube-ide-registers
stmicroelectronics.stm32cube-ide-rtos
twxs.cmake

 

I'll try later to disable / enable extensions one by one to find which one caused the issue

[Julien D]

Thank @Jmace for sharing this list, this is a great starting point to hopefully conclude on something concrete this time. 

[Julien D]

@Jmace, I confirm we have a conflict with one of above extensions. An internal ticket has been created. Thanks for your contribution.