# Problem with Debug Connection running openocd

**URL:** <https://forums.sifive.com/t/problem-with-debug-connection-running-openocd/4775>\
**Category:** HiFive Unmatched\
**Created:** [June 10, 2021, 7:21pm UTC](https://forums.sifive.com/t/problem-with-debug-connection-running-openocd/4775 "2021-06-10T19:21:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CKY](https://avatars.discourse-cdn.com/v4/letter/c/dec6dc/32.png) [@CKY](https://forums.sifive.com/u/CKY)\
**Post date:** [June 10, 2021, 7:21pm UTC](https://forums.sifive.com/t/problem-with-debug-connection-running-openocd/4775/1 "2021-06-10T19:21:02Z")

</div>

We cannot connect to the JTAG/cJTAG when running openocd -f config.cfg file on U74 CPU, but it similar setup works on the U5 CPU, is there any setup differently between U74 and U54 ?

Our error message as follows:

sudo openocd -f jlink\_vcu118\_2.cfg

Open On-Chip Debugger 0.10.0+dev-g7fe6fcfd (2021-06-02-10:35)  
Licensed under GNU GPL v2  
For bug reports, read  
[http://openocd.org/doc/doxygen/bugs.html](http://openocd.org/doc/doxygen/bugs.html)  
adapter speed: 1000 kHz  
Begin jtag newtap:  
TapName Enabled IdCode Expected IrLen IrCap IrMask

* * *

0 riscv.cpu Y 0x00000000 0x\*0000000 5 0x01 0x03  
set block  
target create block  
Error: Invalid command argument  
Error: Invalid command argument  
Error: Invalid command argument  
Error: Invalid command argument  
Error: Invalid command argument  
sudo openocd -f jlink\_vcu118\_2.cfgInfo : J-Link V9 compiled Dec 13 2019 11:14:50  
Info : Hardware version: 9.20  
Info : VTarget = 3.306 V  
Info : clock speed 1000 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: riscv.cpu: IR capture error; saw 0x1f not 0x01  
Warn : Bypassing JTAG setup events due to errors  
Error: Unsupported DTM version: 15  
Info : Listening on port 3456 for gdb connections  
Info : Listening on port 3457 for gdb connections  
Info : Listening on port 3458 for gdb connections  
Info : Listening on port 3459 for gdb connections  
Info : Listening on port 3460 for gdb connections  
Error: authdata\_read is not implemented for this target.

Error: Unsupported DTM version: 15

Thanks,  
CK

---

<div class="post-metadata">

**Author:** ![vmedea](https://avatars.discourse-cdn.com/v4/letter/v/3be4f8/32.png) [@vmedea](https://forums.sifive.com/u/vmedea)\
**Post date:** [July 30, 2021, 1:02pm UTC](https://forums.sifive.com/t/problem-with-debug-connection-running-openocd/4775/2 "2021-07-30T13:02:23Z")

</div>

Did anyone get openocd (over the FTDI JTAG) to work with the Unmatched board? I’m kind of new to openocd (have used it with some ARM board in the far past) and couldn’t find any guide how to configure it for this hardware. Especially for kernel debugging, but even simple things like being able to reset the CPU and inspect memory would be useful.

Edit: I found this, I think it helps: [https://www.reddit.com/r/RISCV/comments/no4a3e/hifive\_unmatched\_openocd\_gdb\_beginning\_bare\_metal/](https://www.reddit.com/r/RISCV/comments/no4a3e/hifive_unmatched_openocd_gdb_beginning_bare_metal/)
