OpenOCD running on a Raspberry Pi can use its GPIOs as a JTAG interface if the module bcm2835gpio is built in:
[url]https://www.openocd.org/doc/doxygen/html/bcm2835gpio_8c_source.html[/url]
The package with added features builds on a Raspberry Pi (armv7h) and OpenOCD works afterwards, also tried the JTAG interface with an actual device.
The PKGBUILD is also missing "sysfsgpio" module and has incorrect architecture (x86_64). This has been reported:
[url]https://archlinuxarm.org/forum/viewtopic.php?f=15&t=16551[/url]
Considering all the fixes the final PKGBUILD for openocd-rpi is:
[code]
_features=(amtjtagaccel armjtagew buspirate ftdi gw16012 jlink oocd_trace opendous osbdm
parport presto_libftdi remote-bitbang rlink stlink ti-icdi ulink usbprog vsllink
aice cmsis-dap dummy jtag_vpi openjtag_ftdi usb-blaster-2 usb_blaster_libftdi bcm2835gpio sysfsgpio)
pkgname=openocd-rpi
pkgver=0.12.0
pkgrel=1
epoch=1
pkgdesc='Debugging, in-system programming and boundary-scan testing for embedded target devices (including bcm2835gpio module to use Raspberry Pi GPIOs as a JTAG interface)'
arch=('armv7h' 'aarch64')
[/code]
...(the following lines of openocd-rpi's PKGBUILD are the same as the original "openocd" PKGBUILD)...