Hi all
After some really frustrating months with the PI DebugProbe (debugging a FreeRTOS application) I've decided to change to the JLink solution, because I've had only good experience (also in professional projects) with the Segger tools.
The DebugProbe had some times outdated binaries started (e.g. a build-timestamp was not that one, what should be printed on the UART), no messages about successfull erase/flash/verify steps and in case of any problem stops instead of jumping to the debug session. Additional the main breakpoint was sometimes not hit after programming, and in case of adding/removing breakpoints during the debug session, they were also never hit.
I've managed to change my launch.json and it seems that it works (I get some downloading and verifying messages![:D]( "Very Happy")
), and the main breakpoint is always hit and stepping works.
A simple sample blink-project and UART-Printfs without FreeRTOS shows no problem using the JLink with this configuration.
But it seems that the FreeRTOS-programm doesn't start correctly (no printf-UART output). And there aren't both cores available in the callstack. Did I missed something?
Best regards
P51D
After some really frustrating months with the PI DebugProbe (debugging a FreeRTOS application) I've decided to change to the JLink solution, because I've had only good experience (also in professional projects) with the Segger tools.
The DebugProbe had some times outdated binaries started (e.g. a build-timestamp was not that one, what should be printed on the UART), no messages about successfull erase/flash/verify steps and in case of any problem stops instead of jumping to the debug session. Additional the main breakpoint was sometimes not hit after programming, and in case of adding/removing breakpoints during the debug session, they were also never hit.
I've managed to change my launch.json and it seems that it works (I get some downloading and verifying messages
), and the main breakpoint is always hit and stepping works.Code:
{ "name": "J-Link", "cwd": "${workspaceRoot}", "gdbPath" : "${userHome}/.pico-sdk/toolchain/14_2_Rel1/bin/arm-none-eabi-gdb.exe", "executable": "${command:raspberry-pi-pico.launchTargetPath}", "servertype": "jlink", "serverpath": "C:/Program Files/SEGGER/JLink_V918/JLinkGDBServerCL.exe", "armToolchainPath": "${userHome}/.pico-sdk/toolchain/14_2_Rel1/arm-none-eabi/bin", "request": "launch", "type": "cortex-debug", "interface": "swd", "serialNumber": "xxxxx", "device": "RP2040_M0_0", "runToEntryPoint": "main", "svdFile": "${userHome}/.pico-sdk/sdk/2.2.0/src/${command:raspberry-pi-pico.getChip}/hardware_regs/${command:raspberry-pi-pico.getChipUppercase}.svd", "postRestartCommands": [ "break main", "continue" ] },But it seems that the FreeRTOS-programm doesn't start correctly (no printf-UART output). And there aren't both cores available in the callstack. Did I missed something?
Best regards
P51D
Statistics: Posted by P51D — Sat Feb 14, 2026 12:01 pm — Replies 1 — Views 61