Package Details: openocd-git 0.12.0.r59.g0b6f53e94-1

Git Clone URL: https://aur.archlinux.org/openocd-git.git (read-only, click to copy)
Package Base: openocd-git
Description: Debugging, in-system programming and boundary-scan testing for embedded target devices (git version)
Upstream URL: http://openocd.org
Licenses: GPL
Conflicts: openocd
Provides: openocd
Submitter: veox
Maintainer: codyps (AndrevS, mdf, flaviut, beppone, arti)
Last Packager: flaviut
Votes: 30
Popularity: 0.000252
First Submitted: 2012-12-30 00:55 (UTC)
Last Updated: 2023-02-03 14:35 (UTC)

Required by (13)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

JasonP commented on 2022-02-10 13:25 (UTC)

Both files are located here: https://repo.or.cz/openocd.git/tree/HEAD:/tcl/target

They belong to the repo for some years now. It could be that some underlying tool used for building the package doesn't support UTF-8 properly. I don't really know. Web browser seems to render fine those characters for instance.

waxar commented on 2021-12-18 05:39 (UTC)

While building, some warnings pop un in regards to Russian letters in filenames:

==> Creating package "openocd-git"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
: Can't translate pathname 'usr/share/openocd/scripts/target/1986ве1т.cfg' to UTF-8: Can't translate pathname 'usr/share/openocd/scripts/target/к1879xб1я.cfg' to UTF-8==> Leaving fakeroot environment.
==> Finished making: openocd-git 0.11.0.r542.gfdf17dba5-1 (Fri 17 Dec 2021 09:34:04 PM PST)
==> Cleaning up...

waxar commented on 2021-12-18 05:36 (UTC)

After building, installing and rebooting, this is what I encounter in the logs:

Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:7 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:14 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:17 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:20 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:23 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:26 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:28 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:31 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:34 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:35 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:38 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:41 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:43 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:46 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:49 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:52 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:53 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:56 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:59 Unknown group 'plugdev', ignoring
Dec 17 21:34:33 seny-arch systemd-udevd[240]: /usr/lib/udev/rules.d/60-openocd.rules:62 Unknown group 'plugdev', ignoring
...

codyps commented on 2020-02-26 00:29 (UTC)

@mdf done

mdf commented on 2020-02-23 19:45 (UTC)

Can you add xlnx_pcie_xvc to features? It enables a new driver I recently submitted.

akurei commented on 2019-04-10 13:02 (UTC)

Please change source to git+https from git+http.

thx1138 commented on 2019-02-03 21:59 (UTC)

/lib/udev/rules.d/60-openocd.rules GROUP="plugdev", TAG+="uaccess"

In contrast, for instance, "/usr/lib/udev/rules.d/69-libftdi.rules" does not use GROUP="plugdev", but only TAG+="uaccess".

André, please address this issue.

https://bugs.archlinux.org/task/35602 and https://bugzilla.redhat.com/show_bug.cgi?id=815093

" Sure, we must entirely get rid of that crap. "plugdev" is a very misguided and fundamentally wrong Ubuntuism."

But, then, Arch is not Fedora. In particular, from the Arch bug, "Note its caveat, it [uaccess] does not work over SSH." I'm very fond of using ssh over wifi when I want a portable keyboard and screen. Still, using ssh is no limitation at all if I am also already logged-in to the machine into which a device is "plugged", as far as I can tell.

Admittedly, this systemd/Fedora recommended "best practice" is either a very old - circa 2012 - or a relatively recent - circa 2018 - change to systemd policy, depending upon a person's opinion about the quality of systemd documentation:

https://github.com/OpenCBM/OpenCBM/pull/8 Use of TAG+="uaccess" instead of GROUP and MODE

https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/ Linux automatic user ACL management

To resolve this, either: getent group plugdev >/dev/null || groupadd -r plugdev

or, preferably: sed -i 's/, GROUP="plugdev"//' "$pkgdir/usr/share/$_pkgbase/contrib/60-openocd.rules"

or:

https://github.com/systemd/systemd/issues/4288 Document the uaccess mechanism / dynamic device permissions

"We should also give some hints for people writing udev rules (e.g. for package maintainers or upstream developers). E.g. if it is ok to use TAG+="uaccess" directly or it's better to use ID_* variables and letting 70-uaccess.rules do the tagging."

Which is to say, after reading through /usr/lib/udev/rules.d/70-uaccess.rules, and then choosing some general class of device from there, which could apply to, say, "JTAG adapters and flash memory programmers", then, instead of applying TAG+="uaccess" directly, apply some new ENV{ID_PLUGDEV}="1" rule, and then plead with systemd "upstream" to modify 70-uaccess.rules to include a custom ENV{ID_PLUGDEV}=="?*", TAG+="uaccess" rule.

Of course, this last alternative seems completely unnecessary and undesirable, but it is another option.

codyps commented on 2018-11-26 03:29 (UTC)

Thanks for reporting Tom. I've added aarch64 to the arch list as suggested.

TomKeddie commented on 2018-11-25 22:01 (UTC) (edited on 2018-11-25 22:01 (UTC) by TomKeddie)

Builds fine for rpi3 by adding aarch64 to the arch list. Thanks, Tom

[tom@rpi3 openocd-git]$ git diff  
diff --git a/PKGBUILD b/PKGBUILD
index c82ddda..a64d90a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,10 +9,10 @@

 _pkgbase=openocd
 pkgname=openocd-git
-pkgver=0.10.0.r523.g2a3b709aa
+pkgver=0.10.0.r581.g1b864d6e4
 pkgrel=1
 pkgdesc="Debugging, in-system programming and boundary-scan testing for embedded target devices (git version)"
-arch=('i686' 'x86_64' 'arm')
+arch=('i686' 'x86_64' 'arm' 'aarch64')
 url="http://openocd.org"
 license=('GPL')
 depends=('libftdi' 'libftdi-compat' 'libusb' 'libusb-compat' 'hidapi' )
[tom@rpi3 openocd-git]$ 

codyps commented on 2018-07-14 23:26 (UTC)

I'd like to second AndrevS's request to change the mirror used. Sourceforge fetch speed is incredibly poor.