2026-05-05 5:20 AM - last edited on 2026-05-05 5:59 AM by Andrew Neil
Hello,
I'm sorry to bother again, but it seems there is another issue in the latest update of VSCode STM32IDE extension. While trying to Start Debugging with GDB Server (STM32Cube Debug STLink GDB Server v1.3.0), with launch.json as:
"version": "0.2.0",
"configurations": [
{
"type": "stlinkgdbtarget",
"request": "launch",
"name": "STM32Cube: STM32 Launch ST-Link GDB Server",
"origin": "snippet",
"cwd": "${workspaceFolder}",
"serverReset": "Connect under reset",
"preBuild": "${command:st-stm32-ide-debug-launch.build}",
"runEntry": "main",
"imagesAndSymbols": [
{
"imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}"
}
],
"faultUnalignedAccess": false,
"liveWatch": {
"enabled": true,
"samplesPerSecond": "4"
},
"preRunCommands": [
"set output 16"
]
}
]
}The Debug starts and I get an error message as:
PARSE ERROR: Argument: -cp (--stm32cubeprogrammer-path)
Argument already set!
Brief USAGE:
C:/Users/.../AppData/Local/stm32cube/bundles/stlink-gdbserver/7.10
.0+st.3/bin/ST-LINK_gdbserver.exe
[--external-init]
[--pend-halt-timeout <Pending halt
timeout>] [--halt] [-c <config
file>] [-e] [-f <log file>] [-l
<log level>] [-p <port number>]
[-v] [-r <refresh delay>] [-s] [-d]
[-z <port number>] [-a <cpu clock>]
[-b <SWO CLOCKDIV>] [-k] [-q] [-i
<ST-LINK S/N>] [-m <apID>] [-g]
[-t] [--erase-all] [--memory-map
<device id>] [--ext-memory-loaders]
[-ei <file_path>] ... [-el
<file_path>] ... [-cp <path>]
[--temp-path <path>]
[--preserve-temps] [--frequency
<max freq kHz>] [--licenses] [--]
[--version] [-h]
For complete USAGE and HELP type:
C:/Users/.../AppData/Local/stm32cube/bundles/stlink-gdbserver/7.10.0+st.3/bin/ST-LINK_gdbserver.exe --help
cube has exited with code 1GNU gdb (GNU Tools for STM32 13.3.rel1.20250523-0900) 14.2.90.20240526-git
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.If I switch to older version v1.2.0, there is no issue.
I'm using STLink V3SET. I have tried to generate new STLink GDB Server Configuration, but the issue is still there on v1.3.0. Also I have tried to: Set Up STM32Cube project(s) again, with no luck too.
Thanks for looking into it.
2026-05-05 6:07 AM
I have the same problem.
2026-05-05 6:28 AM
Hi @Michael12 , @dalbiero-BW
I see @Michael12 that you are using ST-Link GdbServer 7.10.0+st.3 with your project.
Is it the same for you @dalbiero-BW ?
Could you please open the bundle manager of your project ("STM32Cube" activity bar > "stm32cube bundle manager" view in the left panel) and update the ST-Link GdbServer for your project?
Please also update to the latest available programmer.
Kind regards,
/Flo
2026-05-05 6:41 AM
I updated `stlink-gdbserver` to 7.13 and `programmer` to 2.22 and now everything works!