@gmx Good fix!It looks fine, just it's Pico 1, (RP2040) right ?
Thought RP2350.
You can try another method of reset:@breaker: I think monitor reset init injects the breakpoints.Code:
"adapter speed 5000; program \"${command:raspberry-pi-pico.launchTargetPath}\" verify; reset halt ; rp2040.core1 arp_reset assert 0 ; rp2040.core0 arp_reset assert 0 ; exit"
As far as command line GDB via OpenOCD and the Debug probe, I have found that while debugging ot running something, monitor reset halt will halt execution at that point, then I do load to load a newly compiled version of the code, then either, continue, or monitor reset init, continue, where init actually re-initializes the RP2040, but halt does not. To start at the beginning of a program without using init, you can issue a set $pc=0x10000000 then continue. I still have much to learn with GDB though.
Code:
monitor reset haltloadset $pc=0x10000000continue
Code:
ctrl-cmonitor reset haltfile <path/your_file.elf>loadmonitor reset initcontinue
Statistics: Posted by breaker — Tue Dec 10, 2024 9:12 pm