Re: [OpenOCD-user] J-LINK problem

[Tommy M. <tom...@ho...>]

> tried a script
> #!/bin/sh program=openocd
> config=/usr/local/share/openocd/scripts/interface/jlink.cfg
> target=/usr/local/share/openocd/scripts/target/stm32g0x.cfg
> $program -f $config -f $target -c "init" -c "reset" -c "exit"
>
> got:
>
> Open On-Chip Debugger 0.12.0
> Licensed under GNU GPL v2
> For bug reports, read
>          http://openocd.org/doc/doxygen/bugs.html
> Info : auto-selecting first available session transport "jtag".  To override use 'transport select <transport>'.
> Error: No J-Link device found

Does a verbose `openocd -d3` provide any additional details?
Does `sudo openocd...` behave any differently?
What does `lsusb` show for the J-Link?
If you build OpenOCD from the latest source repository does it behave any differently?