SWD debugging in VSCode

[AndyM15]

In general the bootloader is doing a great job. My project is running very well together with it. But now I tried to debug the project using VSCode and the official extension for Pi Pico. I could break it down to a very simple blinking LED project. As soon I add the bootloader, debug stops working. Without I can set breakpoints and everything.
My guess would be that the breakpoint addresses no longer match together with the bootlader. But that's above my knowledge...

[JZimnol]

I'm glad to hear that you like the bootloader!

Unfortunately, I've never used the VSCode Pico extension. I've been using openocd + gdb SWD terminal debugging and it works well, so the problem is with the Pico extension itself probably.
Generated app's .elf file has properly adjusted addresses after building the app with the bootloader. Either the VSCode uses incorrect .elf file for the debugging or the breakpoints are not being set properly by the VSCode/extension.

[AndyM15]

Have the same problem with openocd+gdb. Maybe you can spot something...?

[JZimnol]

Can you provide me with the exact command you use to run openocd and gdb?

[AndyM15]

openocd.exe -f interface/cmsis-dap.cfg -f target/rp2040.cfg
arm-none-eabi-gdb.exe build/PicoDebugTest.elf

[JZimnol]

Is the app running (the LED is blinking) after you run it with the GDB?

I don't know what may be the cause of that. I will try to look into it in the near future.

[AndyM15]

After monitor reset init and continue, yes. But the breakpoints always getting ignored..
Thank you!

[JZimnol]

I've tested it locally (Linux) and everything seems to work fine. The only difference is I'm using gdb-multiarch instead of arm-none-eabi-gdb.
I'm using 0.12.0+dev-gebec9504d version of openocd and 12.1 version of gdb-multiarch. pico-sdk version 1.5.1.
Tested on github.com/JZimnol/pico_fota_example.

[AndyM15]

I found a Windows build of gdb-multiarch, tried it, but everything pretty the same. Not yet tried your example.