I use the homemade debug probe, load the program into the target Pico, and debug it.
Works well.
But how do I get a compilation result into the Pico without using debugging?
Currently, I use a command to load like this:I execute it in a second terminal window in VS Code.
Everything works fine, but I wonder if there is already an integration or a hack to change the current ‘run’ script from “picotol” to ‘openocd’?
In principle, something is already there, e.g., in /.vscode/tasks.json or /.vscode/launch.json
1) Is there something available already / How do you do it?
2) The "adapter speed 5000" doesn't sound very high. Are there any reasonable ways to increase it?
cheers,
martin
Works well.
But how do I get a compilation result into the Pico without using debugging?
Currently, I use a command to load like this:
Code:
./openocd -s ./scripts -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c “adapter speed 5000” -c “program e:/Documents/1a_VSCode/dualDDStoPWMv01/build/dualDDStoPWMv01.elf verify reset exit”Everything works fine, but I wonder if there is already an integration or a hack to change the current ‘run’ script from “picotol” to ‘openocd’?
In principle, something is already there, e.g., in /.vscode/tasks.json or /.vscode/launch.json
1) Is there something available already / How do you do it?
2) The "adapter speed 5000" doesn't sound very high. Are there any reasonable ways to increase it?
cheers,
martin
Statistics: Posted by MartinHill — Thu Feb 12, 2026 7:05 pm — Replies 2 — Views 58