# The one line that names the JTAG adapter, for every board config in this image.
#
# The VF6 manufacturing station funnels every per-SOM config through a file of
# this name (projects-internal, branch vf6-mfg,
# manufacturing/openocd-0.9.0/mfg-jtag.cfg, 150 bytes and one `source`), and the
# seam is kept here on purpose: the bench adapter and the WebUSB grant have to
# name the same device, and this is the single place that decides which.
#
# The station's own copy points at olimex-arm-usb-ocd-h.cfg, and the `-ocd-h-`
# in its board filenames is legacy naming rather than the adapter in use. The
# bench here runs an ARM-USB-TINY-H (15ba:002a) -- the device BRINTOS-2752
# enumerated over WebUSB and BRINTOS-9 clocked JTAG through -- so that is the
# default below.
#
# A station with a different adapter overrides it instead of editing this file,
# because a machine's filesystem is per-session: an edit here survives only if
# the session is published as a snapshot, which costs a full image copy. So:
#
#     som-program-f7 --adapter olimex-arm-usb-ocd-h
#     openocd -c "set BRINTOS_JTAG_IFACE interface/ftdi/<file>.cfg" -f <board>
#
# The variable is read while this file is being sourced, so it must be set
# before -f. openocd's own interface/ftdi/ ships the other Olimex models
# (olimex-arm-usb-ocd-h, olimex-arm-usb-ocd, olimex-jtag-tiny,
# olimex-arm-jtag-swd), so an override names a file that is already installed.
if {![info exists BRINTOS_JTAG_IFACE]} {
    set BRINTOS_JTAG_IFACE interface/ftdi/olimex-arm-usb-tiny-h.cfg
}
source [find $BRINTOS_JTAG_IFACE]