Hi @Visques,
There is a difference between "hot attach" and "request attach.":
Hot attach: The GDB server is launched by the adapter (i.e., at the start of the debug session) with no reset and no download. You need to load the symbols at least to debug, using the attribute "imagesAndSymbols" -> "symbolFileName".
This is the use case you described.
Request attach: The GDB server is already running, and you connect to it either remotely or locally.
That’s why only a few server attributes are available in the debug configuration, because the adapter does not manage the server launch.
So, for your use case, it is the hot attach. You can set the serverJtagCfg attribute using the request launch:
{
"type": "jlinkgdbtarget",
"request": "launch",
"name": "STM32Cube: STM32 Launch JLink GDB Server",
"origin": "snippet",
"cwd": "${workspaceFolder}",
"preBuild": "${command:st-stm32-ide-debug-launch.build}",
"runEntry": "main",
"serverReset": "None",
"serverInterface": "JTAG",
"serverJtagCfg": "9,2",
"imagesAndSymbols": [
{
"symbolFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}"
}
]
}
Note: I just saw that you already asked this question in our previous thread, my bad, I missed the notification.
KR,
Flo
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.