The latest OpenOCD fails on running for EMSK

[kolerov]

I try to run the latest OpenOCD for EMSK v2.2 and I see this:

$ openocd -f board/snps_em_sk_v2.2.cfg
Open On-Chip Debugger 0.12.0+dev-gffa52f0e0 (2023-08-02-10:41)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: unable to open ftdi device with description 'Digilent Adept USB Device', serial '*' at bus location '*'

The problem is in share/openocd/scripts/interface/ftdi/digilent-hs1.cfg file. The latest one (1.2) contains this:

# SPDX-License-Identifier: GPL-2.0-or-later

# this supports JTAG-HS1 and JTAG-SMT1
# (the later being the OEM on-board version)

adapter driver ftdi
ftdi device_desc "Digilent Adept USB Device"
ftdi vid_pid 0x0403 0x6010
# channel 1 does not have any functionality
ftdi channel 0
# just TCK TDI TDO TMS, no reset
ftdi layout_init 0x0088 0x008b
reset_config none

The old one (from 0.9) contains this:

#
# Digilent HS1
#
# The Digilent HS1 is a high-speed FT2232H-based adapter, compliant with the
# Xilinx JTAG 14-pin pinout.
# It does not support ARM reset signals (SRST and TRST) but can still be used for
# hardware debugging, with some limitations.
#
# http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,395,922&Prod=JTAG-HS1
#

interface ftdi
ftdi_vid_pid 0x0403 0x6010
ftdi_layout_init 0x0088 0x008b

After changing Digilent Adept USB Device string to Digilent USB Device everything works fine. Also, I tried changing source [find interface/ftdi/digilent-hs1.cfg] string to source [find interface/ftdi/snps_sdp.cfg] in share/openocd/scripts/board/snps_em_sk_v2.2.cfg file and faced another problem:

Open On-Chip Debugger 0.12.0+dev-gffa52f0e0 (2023-08-02-10:41)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 5000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: arc-em.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : starting gdb server for arc-em.cpu on 3333
Info : Listening on port 3333 for gdb connections

I can connect to the board using GDB but loading fails.