-
Notifications
You must be signed in to change notification settings - Fork 246
Probe speed stuck at very low frequency #161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
How are you connecting the probe to the target (electrically)? |
I felt dumb for a moment thinking i did not try to solder wires directly from the probe to the target, as i only connected them via jumpers beforehand. But, then i tried to solder them and unfortunately im running into the exact same issue. |
Sketch your connections. |
Sorry for the delay. I'm following the documentation and double checking it with the pin definitions in board_pico_config.h.
|
5MHz definitely isn't going to work with that sort of setup. 30kHz is a bit low but not unsurprising. Connect the centre GND pin on the SWD/SCLK header on the Pico W to the GND on the RP2040-zero. Twist the SWD/SWCLK wires together with the GND wire. It should go a bit faster. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Those few past days i've been trying a combination of rp2040 and rp2350 as both host and guest (debugger & target).
I've got myself a mix of 4+ different 2040s, in both the official dev board and some other custom formats, spanning different revision.
No matter what software im using (openocd, pyOCD, probe-rs), i'm stuck with a speed that ranges between 10khz and 30khz, with 10 being the one that consistently works and 30 being somewhat unreliable where it could fail at some point during the flashing process.
Unfortunately i dont have any other debugger available to confirm that it is in fact an issue with debugprobe, but i dont know what else to look for so i'm opening this issue in the hope that its something known and workaround-able.
I've also tried with older revisions, going back to 1.0 but no difference at all.
That being said i've only tried interfacing with debugprobe on Windows, not sure if this could be the issue.
This is when i run it at 10khz
openocd -f interface/cmsis-dap.cfg -c "set USE_CORE 0" -f target/rp2040.cfg -c "adapter speed 10"
And this is when running at the classic 5000khz
openocd -f interface/cmsis-dap.cfg -c "set USE_CORE 0" -f target/rp2040.cfg -c "adapter speed 5000"
The text was updated successfully, but these errors were encountered: