<toobah>
i think what it's saying in the howto/openocd.mb is that you need to build the https://github.com/raspberrypi/openocd port, and i tried that, but the first thing i got after running `openocd -f board/pico-debug.cfg` was `invalid command name "script"`
<toobah>
sorry if my explanation might be kinda crappy messing w this has fried my brain.
<josuah>
hi toobah!
<josuah>
I am currently ongoing through that as well
<josuah>
you do not need to build raspberrypi openocd port: the author of pico-debug (majbthrd) did a wonderful work (unrelated to the Raspbery Pi foundation) for getting support for CMSIS-DAP standard protocol
<josuah>
the raspberrypi/openocd is there for specifically supporting their board through using another board: the picoprobe project
<josuah>
this project could have been a good idea, but is instead using a proprietary protocol "picoprobe" instead of the common-place USB standard CMSIS-DAP
<toobah>
i am literally praising god rn
<josuah>
the raspberrypi/openocd.git fork is lacking so much behind that the pico-debug made its way onto openocd.org's master, which now has the pico-debug support upstream
<toobah>
so pico-debug.cfg should be in the regular openocd distro?
<josuah>
so you can either use the FreeBSD package, or using the latest openocd git master
<josuah>
Also, the latest git version of raspberrypi/openocd did try to integrate some commits from openocd, but did not cover the TCL scripts which were not updated needingly
<josuah>
at least so I think, so the rp2040 branch of raspberrypi/openocd did not work for me
<josuah>
better forget using one raspberrypi to debug another via picoprobe, and go for pico-debug
<toobah>
i wasnt using picoprobe, i was simply misguided
<toobah>
and thank fknn god
<toobah>
I DONT WANNA
<toobah>
although the only reason i think i tried it was because it didnt seem like the openocd port had pico-debug.cfg
<josuah>
pico-debug.cfg along with some changes in the C source code maybe. openocd works very well on OpenBSD (here), should work even better on FreeBSD ;)
<toobah>
ur pretty badass tbh i dont ever meet people who use bsd
<josuah>
toobah: it depends on where I guess, never met one AFK
<josuah>
FYI: here is the next step where I am stuck on my side:
<josuah>
Info : Listening on port 6666 for tcl connections
<josuah>
another effort for bringing CMSIS-DAP to the RP2040, this time using a first RPi Pico to debug another one
toobah has quit [Ping timeout: 256 seconds]
toobah has joined #openocd
<toobah>
so i just reinstalled `/usr/ports/devel/openocd`, and interestingly it doesn't seem to have `board/pico-debug.cfg`... is it under a dif name or did i just misunderstand?
tsal has quit [Ping timeout: 272 seconds]
tsal has joined #openocd
<josuah>
maybe the /usr/ports/devel/openocd is less recent than the few latest changes that brought RP2040 support?
<josuah>
in that case, either modifying the port or getting it compiled manually could do the trick
<toobah>
yeah, it's probably just a lil behind tbh
sbach has quit [Read error: Connection reset by peer]
sbach has joined #openocd
nerozero has joined #openocd
<josuah>
toobah: I went AFK, what is that error you have?
<josuah>
toobah: could you copy that pico-debug.cfg on a local directory, try again with openocd -f ./pico-debug.cfg, then paste the pico-debug.cfg on a pasteboard?
<josuah>
"script" seems used in some script where "source" would be more fit (or maybe I do not know TCL enough)
<josuah>
so in case you are stuck with it, you may try replacing script with source and see the outcome
<josuah>
no idea why it would cause any error...
<josuah>
you may also paste the git commit hash so that it is easier to check on an verified identical code base on another system
m has joined #openocd
Haohmaru has joined #openocd
toobah has quit [Quit: Client closed]
toobah has joined #openocd
<toobah>
sorry I also went afk
<toobah>
if you could send your commit hash i would appreciate it, cuz I can't copy paste mine easily
<toobah>
according to the man page, OpenOCD's -f <file> option is a synonym for -c "[script <file>]" which makes me believe that's where the error is?
<toobah>
I can't be entirely sure since you cant emit a tcl trace afaik
<PaulFertser>
toobah: with -d3 it should be visible what commands are getting run and what files are used.
<PaulFertser>
toobah: -f should be equivalent to "source [find ...]"
toobah has quit [Quit: Client closed]
toobah has joined #openocd
<toobah>
from what everyone is telling me im starting to think my OpenOCD is behind lmfao
toobah has quit [Client Quit]
toobah has joined #openocd
toobah has quit [Ping timeout: 256 seconds]
toobah has joined #openocd
toobah has quit [Client Quit]
toobah has joined #openocd
toobah has quit [Client Quit]
toobah has joined #openocd
<toobah>
yeah, I just double checked the manpage, and it definitely states "-f <filename>" is 'shortcut' for `-c "[script filename]"`
toobah has quit [Client Quit]
Bertl_zZ is now known as Bertl
toobah has joined #openocd
toobah has quit [Ping timeout: 256 seconds]
toobah has joined #openocd
cambrian_invader has quit [Ping timeout: 252 seconds]
toobah has quit [Client Quit]
m has quit [Remote host closed the connection]
toobah has joined #openocd
<toobah>
man this whole build is fucked
<toobah>
just running `openocd` with no args gives `invalid command name "init_targets"`