On 10/09/2026 11:13, Paul Jewell wrote:
Good morning,
I am transferring development of programming for a Black Pill ARM board from my
linux machine to an OpenBSD laptop, as part of my plan to move away from Linux.
I am getting an error message when uploading to the board:
---------------------------------8<---------------------------
apollo$ make upload
openocd -f interface/stlink.cfg -f target/stm32f4x.cfg -c "program blink.elf verify
reset exit"
Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Warn : Could not determine executable path, using configured BINDIR.
Info : auto-selecting first available session transport "hla_swd". To override use
'transport select <transport>'.
Info : The selected transport took over low-level target control. The results
might differ compared to plain JTAG/SWD
Info : clock speed 2000 kHz
Error: open failed
in procedure 'program'
** OpenOCD init failed **
shutdown command invoked
----------------------------------8<--------------------------
At the moment I am using the same Makefile which works under Linux. I fully
appreciate that I may have not setup access to the USB port properly for my
user account, or that this may be an issue with OpenOCD usage under OpenBSD.
However, I have not been lucky in finding more documentation to help me.
If any of you could point me at a location for documentation, or ideally a
trivial working project using OpenOCD to upload via stlink, that would be great.
Many thanks!
Paul
Sorry - re-reading my message reminded me that if the issue is user
access to the USB port, then doing the same thing as root should work.
Indeed, it did, so I need to understand how to allow user write access
to the usb ports, and I guess that is in the OpenBSD documentation.
Apologies for the noise!
Paul
