03:39 <Guest35> Hello - anybody home??

03:56 <Guest35> I'm using openocd with my RPi Pico dev kit, hosted on an RPi5. Which config file do I need to use to set the "adapter speed"? Alternatively, how would I go about creating a config file to retain the '-c' settings I now enter at the command line?

03:59 <Hawk777> You can just put each thing you pass to “-c” into a file, one item per line.

03:59 <Hawk777> The syntax between “-c” options and config files is the same.

04:06 <Guest35> OK - "into a file"... but which file?

04:27 <Hawk777> Whatever file you want. That’s your new config file. You tell OpenOCD to read it with “-f” on the command line.

04:28 <Guest35> Let me try that...

04:47 <Guest35> Here's the command line I've been using: 'sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "program ina260_trial.elf verify reset exit"'   ... It works except that it uses the default x-slow 100kHz speed. If I add the following option, it goes faster: `-c "adapter speed 5000"'.                         I've

04:47 <Guest35> tried adding this to the 'target/rp2040.cfg' file, but it ignores all variations of `-c "adapter speed 5000"' I've tried. Should I use a 'set' instead of '-c'??

04:54 <Guest35> Also - I have two copies of the rp2040.cfg file on. my system:  One at '/home/pi/pico/openocd/tcl/target/rp2040.cfg', and another at

04:54 <Guest35> '/usr/local/share/openocd/scripts/target/rp2040.cfg'  Since I'm having to use sudo to run openocd, maybe it's the file in '/usr/local/share...' that I should be modifying??

05:01 <Guest35> OK - that's what was wrong... I was editing the "wrong" copy of 'rp2040.cfg' !?! If I add 'adapter speed 5000' to the file '/usr/local/share/openocd/scripts/target/rp2040.cfg' I don't get the warning from openocd, and the program loads much faster.

05:03 <Hawk777> Oh, no, don’t put the “-c” itself in the config file.

05:03 <Hawk777> Just the “adapter speed 5000” command.

05:03 <Hawk777> Ah there you go.

05:03 <Guest35> But that raises another question, "Why is openocd reading from the 'rp2040.cfg' file at '/usr/local/share' instead of the file at 'home/pi/pico'?

05:04 <Hawk777> If you want to write a local file of your own, probably best to name it something else.

05:04 <Hawk777> It has a search path where it looks for shipped config files, and I’m not sure whether it looks there or in the current working directory first.

05:05 <Guest35> Do you know where the search path is specified? It's not PATH I presume...?

05:24 <Guest35> Well shit fire & save matches... I can't seem to overcome the sudo requirement. I 'chown'd the rp2040.cfg file, but then openocd threw this error: "Error: unable to find a matching CMSIS-DAP device"...   I 'chown'd the 'usr/local/share/openocd/interface/cmsis-dap.cfg' , but that didn't fix it. Grrrr!

06:00 <Hawk777> It’s not $PATH. I’m not sure what it is.

06:00 <Hawk777> The error you’re seeing now is not about accessing the config files, it’s about accessing the actual USB devices.

06:01 <Hawk777> These would probably be device nodes in /dev/bus/usb. You could either set up a udev rule to grant access to your JTAG adapter to your regular user, or depending on your Linux distro, there may be a group you can add yourself to which will do that.

08:52 <karlp> sudo cp /home/pi/pico/openocd/contrib/60-openocd.rules /etc/udev/rules.d && sudo udevadm control --reload; [unplug and replug your adapter here]

08:52 <karlp> it's using the files in /usr/local/share, because you installed it.

08:52 <karlp> and ar erunning "openocd"

08:53 <karlp> if you want to see the search path a given installation of openocd will use, the easiest way I know is "openocd -f hohoho -d3"

08:59 <Seamus> karlp  ummm... I was here earlier under a different nickname, asked a couple of questions, then got distracted with registration, etc. I wonder if your answers were to the questions I asked?

10:04 <karlp> did they sound useful? :)