“Device-specific files” folder includes version number but shouldn’t

[andrewn]

I have an existing STM32H7 project which builds using the true arm-eabi path:

%LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32

on the disk. However in Visual Studio, the include files, though all present, refer to

%LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\2022.01

which doesn’t exist! According to the .filters file, this is set from the BSP_ROOT macro in VS which seems to be getting it right for a build but not for the coding environment.

Given that other than the release folder being added to the path, the files all look to be in the same hierarchy, how can this be fixed?

Kind thanks.

[support]

Hi,

This probably happened because the project was created when the BSP was installed in the single version mode. Then the BSP got switched to the multi-version mode via VisualGDB Package Manager, that resulted in moving the files to the version subfolder.

If you are using GNU Make or MSBuild, the .vcxproj file has to explicitly reference the exact sources from the BSP, so you would need to update it via VisualGDB Project Properties -> Embedded Project -> Regenerate MCU Files. CMake-based projects just reference the BSP version and compute all paths dynamically, so they don’t need any changes.

[andrewn]

Perfect, thanks. I was floundering in the right area but couldn’t work out what the fix was.

[Author]

Posts