Support for STM32CubeCLT

[srberard]

Is your feature request related to a problem? Please describe. I'm working with the STM32CubeCLT tools from ST Micro. STM32CubeCLT is a toolset for third-party integrated development environment (IDE) providers, allowing the use of STMicroelectronics proprietary tools within their own IDE frameworks.

I am using these instead of the STM32CubeIDE as I'm using this under WSL2 with VS Code. I've had issues with the full IDE under WSL and found these instructions on how to setup the CLT tools with WSL.

All of this works, however, I have to manually set the configuration values as the paths are not automatically found. While this works, it needs to be updated every time the tool version changes. Cortex Debug is able to automatically find the paths for the tools under the full IDE.

Describe the solution you'd like I'd like Cortex Debug to automatically detect the path when using the CLT. It is my understanding that the CLT is the recommended toolset when using 3rd party IDEs such as VS Code.

Describe alternatives you've considered Manual configuration of Cortex Debug parameters. In my case, I've installed STM32CubeCLT version 1.17.0. This requires me to set the following parameter:

"cortex-debug.stm32cubeprogrammer.linux": "/opt/st/stm32cubeclt_1.17.0/STM32CubeProgrammer/bin",

I believe Cortex Debug assumes a base path of STM32CubeIDE_ and the CLT uses a different base install path.

Additional context Information on the STM32CubeCLT tools can be found here.