Problem with loading hello world demo on ibex demo system

HiFive Unmatched
1

I am trying to use the IBEX demo system from this repository and load the hello world program to it. My board is an arty a7 100. I went for the native python environment build (didn’t bother with the docker). I am executing the commands as said on the README and I’m getting the following errorafter executing ./util/load_demo_system.sh run ./sw/build/demo/hello_world/demo

Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Error: expected exactly one argument to ftdi_device_desc <description>
force hard breakpoints
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 10000 kHz
Info : JTAG tap: riscv.cpu tap/device found: 0x13631093 (mfg: 0x049 (Xilinx), part: 0x3631, ver: 0x1)
Error: dtmcontrol is 0. Check JTAG connectivity/board power.
Warn : target riscv.cpu examination failed
Info : starting gdb server for riscv.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error: Target not examined yet

Here is the output of lsusb command:
Bus 001 Device 005: ID 0403:6010 Future Technology Devices International, Ltd FT2232C/D/H Dual UART/FIFO IC

And here is the arty-a7-openocd-cfg.tcl file I am using:

# Copyright lowRISC contributors.
# Licensed under the Apache License, Version 2.0, see LICENSE for details.
# SPDX-License-Identifier: Apache-2.0


adapter driver ftdi
transport select jtag

ftdi_device_desc "Future Technology Devices International, Ltd FT2232C/D/H Dual UART/FIFO IC" #"Digilent USB Device"
ftdi_vid_pid 0x0403 0x6010
ftdi_channel 0
ftdi_layout_init 0x0088 0x008b
reset_config none

# Configure JTAG chain and the target processor
set _CHIPNAME riscv

# Configure JTAG expected ID
# arty-a7-35t
# set _EXPECTED_ID 0x0362D093 
# arty-a7-100t
set _EXPECTED_ID 0x13631093


jtag newtap $_CHIPNAME cpu -irlen 6 -expected-id $_EXPECTED_ID -ignore-version
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME riscv -chain-position $_TARGETNAME

riscv set_ir idcode 0x09
riscv set_ir dtmcs 0x22
riscv set_ir dmi 0x23

adapter speed 10000

riscv set_prefer_sba on
gdb_report_data_abort enable
gdb_report_register_access_error enable
gdb_breakpoint_override hard

reset_config none

init
halt
2

You probably need to post a verbose OpenOCD log (openocd -d3 ...) but dtmcontrol is 0 usually means that your debug block hardware is not properly functional (e.g. not clocked, stuck in reset etc.) or the debug probe is not connected properly (as per the message).