Er, no. Those were all taken care of. The problem with the default install and provided config files is that they specify direct access to GPIO hardware witch cannot be updated for the Pi5 since GPIO hardware has moved off chip. As cleverca22 states it should be possible to do it via the JST debug connector on the P5, but that requires a modification of the bit bang driver itself and not just the content of a config file.That may be due to the fact that there is currently no config file for the RPi5 in ~/pico/openocd.I think I wrote about this somewhere here before, but no OpenOCD using the default BRCM bit bashing driver will not work for direct Pico SWD to GPIO debug connection on the Pi5. You can recompile OpenOCD to include the linuxgpiod driver on the Pi5 but it is very slow. I've a debug probe that I've never tried but I suspect it's not much faster. Maybe someone can chime in with the KB/second programming speed using the probe?
In the end I've opted for a dedicated Pi4 to run OpenOCD, and run builds and GDB from a more powerful SBC (such as a Pi5) and tell GDB to remotely connect to OpenOCD on the Pi4 remotely via IP. Not ideal, but gives me faster builds as well as faster image downloads to the Pico.
Statistics: Posted by lurk101 — Fri Jan 26, 2024 12:55 am