Hi all,
I have a project that needs to be in RAM for speed, so I have set set(PICO_COPY_TO_RAM 1) in the CMakeFile. This works as needed, except that if I try and debug the code with breakpoints set they seem to be ignored. I'm debugging with vscode on linux linked accross the network to a debug probe running on another linux computer. This works fine for programming and for debugging in flash but with the code in RAM the breakpoints are ignored.
The section of my launch.jason for this target is :
Is there a solution for this?
Cheers.
Phill.
I have a project that needs to be in RAM for speed, so I have set set(PICO_COPY_TO_RAM 1) in the CMakeFile. This works as needed, except that if I try and debug the code with breakpoints set they seem to be ignored. I'm debugging with vscode on linux linked accross the network to a debug probe running on another linux computer. This works fine for programming and for debugging in flash but with the code in RAM the breakpoints are ignored.
The section of my launch.jason for this target is :
Code:
{ "name": "Pico Debug (remote rp2350)", "type":"cortex-debug", "cwd": "${workspaceRoot}", "executable": "${command:cmake.launchTargetPath}", "request": "launch", "servertype": "external", // This may need to be arm-none-eabi-gdb depending on your system "gdbPath" : "gdb", // Connect to an already running OpenOCD instance "gdbTarget": "trion.ftt:3333", "svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2350.svd",// "runToMain": true, // Work around for stopping at main on restart "postRestartCommands": [ "break main", "continue" ] }Cheers.
Phill.
Statistics: Posted by PhillHS — Sun Dec 14, 2025 9:43 pm