Recently installed the Keil Studio Pack on Visual Studio Code (on Windows 11). I've been able to successfully import existing projects from μVision 5 and build them.
But I'm not able to flash the generated .axf files. The device is properly detected by Arm Device Manager (a NUCLEO-L432KC board), but when I press DEBUG on the CMSIS activity, I get:
Executing task: Flash Device
Error: UNKNOWN: unknown error, stat '\\Users\XXXXX\MICR\E7\out\MICR\mbedNUCLEOL432KC\MICR.axf'
The terminal process terminated with exit code: 1.
Note that file c:\Users\XXXXX\MICR\E7\out\MICR\mbedNUCLEOL432KC\MICR.axf does really exist in the filesystem.
Any clue, I'm stuck here.
Thanks a lot and regards.
Some more insight.
I've enabled VSCode setting "Restrict UNCAccess" and now I get error:
* Executing task: Flash Device
UNC host 'users' access is not allowed. Please update the 'security.allowedUNCHosts' setting if you want to allow this host.
* The terminal process failed to launch (exit code: 1).
So it seems that the UNC '\\Users\XXXXX\MICR\E7\out\MICR\mbedNUCLEOL432KC\MICR.axf' is ill formed, as 'Users' is being interpreted as a server name.
Apparently, the UNC needs to be something like '\\localhost\C$\Users\XXXXX\MICR\E7\out\MICR\mbedNUCLEOL432KC\MICR.axf' instead of '\\Users\XXXXX\MICR\E7\out\MICR\mbedNUCLEOL432KC\MICR.axf'. I do not have a clue where to touch to change that.
Finally verified that it seems to be a bug in v1.0.12 of the Arm Embedded Debugger extension to Visual Studio Code. Downgrading it to v1.0.11 or v1.0.10 works, but not with v1.0.12.
Will report it as a possible bug.
Thanks a lot for sharing your experience with us. Let me know if you need help to report this issue.
A new version (v1.0.13) of the Arm Embedded Debugger extension has been released. This should have fixed the issue that you had experienced on Windows OS.
Thanks for making us aware of this.