VSCode launch.json for running/debuging with flash offset

[Javier1]

 

I’m currently developing a template to help developers debug code located at address 0x8011000 using VSCode.
So far, I haven’t had any success getting the debugger to work properly.

The .elf file itself is fine, when I flash it using STM32CubeProgrammer and enable "Run after programming", the code executes as expected.

I’ve tried multiple solutions, including suggestions from ChatGPT, but nothing has worked yet.

 

[Cartu38 OpenDev]

Not sure to understand what you are tryi.g to do here. Please be explicit more. Maybe a chance to get help then.

[Javier1]

I changpticed it for you @Cartu38 OpenDev , i was tired and not good articulating my problem

[Javier1]

Got it to work, in case someone has a similar issue: 
In my case Reset_Handler is defined in startup_stm32g474xx.s

launch.json 

{
 "version": "0.2.0",
 "configurations": [
 {
 "name": "Debug UserApp at an offset (no full reset)",
 "type": "cortex-debug",
 "request": "launch",
 "servertype": "stlink", // you're using ST-LINK GDB server, not openocd
 "executable": "build/Debug/${workspaceFolderBasename}.elf",
 "device": "STM32G474RE",
 "gdbPath": "arm-none-eabi-gdb",
 "runToEntryPoint": "Reset_Handler",
 "postLaunchCommands": [
 "monitor halt",
 "break main"
 ],
 "overrideLaunchCommands": [
 "load"
 ],
 "showDevDebugOutput": "raw"
 }
 ]
}

tasks.json 

{
 "version": "2.0.0",
 "tasks": [
 {
 "label": "flash-userapp",
 "type": "shell",
 "command": "STM32_Programmer_CLI",
 "args": [
 "-c", "port=SWD",
 "-w", "build/Debug/${workspaceFolderBasename}.elf", // or .hex or .bin
 "-rst"
 ],
 "problemMatcher": []
 }
 ]
}

 

[Cartu38 OpenDev]

Thanks for sharing.

I note you are not using latest extension set proposal : https://community.st.com/t5/stm32cube-for-visual-studio-code/new-stm32cube-for-visual-studio-code-extenstion-released-3-5-1/td-p/819484

[Javier1]

good catch