That looks good... Where do I put this 'test.cfg' file?the old way of gpio doesnt work on the pi5I am trying to wire up the SWD, and having an issue. I've wired it up IAW Chapter 5 of the "Getting Started" guide. However, I get an error message I don't quite understand:
the current solution is to use gpiod or a debug probe
https://github.com/raspberrypi/openocd/issues/93Code:
clever@raspberrypi:~ $ cat test.cfgadapter driver linuxgpiodadapter gpio swclk 20 -chip 4adapter gpio swdio 21 -chip 4clever@raspberrypi:~ $ openocd -f test.cfg -f target/rp2040.cfgOpen On-Chip Debugger 0.12.0-g4d87f6dca (2024-01-05-00:08)Licensed under GNU GPL v2For bug reports, read http://openocd.org/doc/doxygen/bugs.htmlInfo : Hardware thread awareness createdInfo : Hardware thread awareness createdInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsWarn : An adapter speed is not selected in the init scripts. OpenOCD will try to run the adapter at the low speed (100 kHz)Warn : To remove this warnings and achieve reasonable communication speed with the target, set "adapter speed" or "jtag_rclk" in the init scripts.Info : Linux GPIOD JTAG/SWD bitbang driverInfo : This adapter doesn't support configurable speedInfo : SWD DPIDR 0x0bc12477, DLPIDR 0x00000001Info : SWD DPIDR 0x0bc12477, DLPIDR 0x10000001Info : [rp2040.core0] Cortex-M0+ r0p1 processor detectedInfo : [rp2040.core0] target has 4 breakpoints, 2 watchpointsInfo : [rp2040.core1] Cortex-M0+ r0p1 processor detectedInfo : [rp2040.core1] target has 4 breakpoints, 2 watchpointsInfo : starting gdb server for rp2040.core0 on 3333Info : Listening on port 3333 for gdb connections
Another question: Since posting my original Q, I've found one of these 'debug-probe' gadgets. About the same time your response arrived, I managed (finally!) to upload a file "button-free" from the Pi5 to the Pico using the following:
Code:
sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "program blink/blink.elf verify reset exit"I don't understand the need for 'sudo' with this, and it seems wrong - but it is needed; something about "unable to find matching CMSIS-DAP device"? Any analysis or comments on this would also be welcome.
Oh - one other thing: I will eventually need to use the debugger, but for right now I'm happy enough just not having to fool around with that BOOTSEL button :)
Statistics: Posted by irishmonk-57 — Tue Jan 23, 2024 8:08 am