2026-02-11 1:19 PM - edited 2026-02-11 1:45 PM
Probably this is trivial, but I just cannot find it.
How to deploy image using CubeIDE for VS Code without debugging?
How to properly configure Build+Deploy only (no debug) task in tasks.json file?
How to configure Build+Deploy with debug task?
Should I use cube cli for that or there is some easier way?
Solved! Go to Solution.
2026-02-12 12:17 AM
@TDJ
Relying on VS Code integrated terminal please have a try
cube programmer -c port=SWD -d <your .elf file>
2026-02-12 12:17 AM
@TDJ
Relying on VS Code integrated terminal please have a try
cube programmer -c port=SWD -d <your .elf file>
2026-02-12 11:41 AM
@vincent_grenetThank you! It may be worth mentioning that a file path like
${workspaceFolder}/build/debug/${workspaceRootFolderName}.elf
does not work on Windows. I had to use build/debug/${workspaceRootFolderName}.elf instead.
It is likely that "cube programmer" cmd does not handle mixed path separators well.
I think it would make sense to create some sort of shortcut under "STM32CUBE KEY ACTIONS".
2026-02-12 11:36 PM
Thank you for reporting.
We are considering the situation. Unfortunately, the key action cannot be the solution. Lot of end users are using the multi-root workspace feature, which allows multiple projects per workspace / unique Visual Studio Code instance. Additional logic is required to safely retrieve the binary file.