Missing CMSIS_PACK_ROOT

[zhaojiying]

bound doStepSettingsValidation 失败：找不到设备：缺少CMSIS_PACK_ROOT

[Julien D]

Seems like CMSIS_PACK_ROOT variable gets somehow corrupted (emptied) between VSCode startup and your debug launch. Your log clearly states that the variable has been well registered at extension init with the expected value on OSX.

Do you have the issue directly after starting VSCode, or only after a period of time?

When it happens, are you able to open the "Setup STM32cube Project(s)" editor without having any errors?

[one-green-apple]

The accepted solution did not help in my case (Windows 11, CubeMX generated default project, extension version 3.7.0), however, what helped was:

• Checking STM32Cube core logs to see

"Configuring CMSIS_PACK_ROOT environment: C:\Users\<USER>\AppData\Local\stm32cube\packs"

• Updating CMakePresets.json "default" preset to include:

"cacheVariables": {
"CMSIS_PACK_ROOT": "C:\\Users\\<USER>\\AppData\\Local\\stm32cube\\packs"
}

[Cartu38 OpenDev]

@one-green-apple please remind us what issue you're facing exactly ...very same popup windows at debug launch time ? or ?

[one-green-apple]

Yes, the issue was that debug launch resulted in the "Missing CMSIS_PACK_ROOT" error window. Updating CMakePresets.json and restarting VSCode solved the issue, though it is possible that the issue was solved by some side effect of doing this.

[Julien D]

Hi @one-green-apple,

Looking at similar topic (https://community.st.com/t5/stm32cubeide-for-visual-studio/bound-dostepsettingsvalidation-failed-device-not-found-error/m-p/849087#M1285) it looks like conflicting extensions exist; CMSIS_PACK_ROOT defined at extensions init gets emptied later on.

Do you confirm that installing STM32Cube extensions in a separate VSCode profile help to workaround the problem ?

If so could you paste the list of extensions you installed within the default profile ?