Arm CMSIS-Toolbox 2.11.0 - uVision debug settings are stored in out

[FerdinandEn]

Type: Bug Report

Describe the bug

• OS and Version: Win 11
• VS Code Version: 1.104.0
• Extension Version: Csolution 1.60.0
• Target Device: STM32

During testing, I noticed that with the new version, the uVision settings are stored in the out directory. This means that they are lost with every clean.

To Reproduce
Steps to reproduce the behavior:

1. use Arm CMSIS-Toolbox 2.11.0
2. Start uVision
3. do settings
4. close uVision
5. clean
6. restart uVision - settings are again default

Note: So that I can test this, I have replaced the files in the cmsis-toolbox directory in the Keil uVision installation with the 2.11.0 files.

[edriouk]

It is a side effect of .cbuild.yml files being relocated to the /out folder (starting 2.11.0).
uVision saves it's files (*.uvpdbgx, *.uvoptx and `*.uvguix.) side by side. We are currently reviewing where to best place those uVision files, probably in an independent sub folder.

[FerdinandEn]

@edriouk Thanks for the information.

This storage location is disadvantageous because every rebuild or clean deletes the setting parameters for uVision and also for DebugConfig. For me, the best storage location would be the directory where the cproject file is located.