【救命求助】K3 openocd连接一直失败

K3
1

  1. 参考文档链接
    SpacemiT

  2. 按照文档去掉J-Link跳线帽。

    JLINK_remove_jumper
    JLINK_remove_jumper1920×2560 376 KB

  3. Linux系统。拷贝60-openocd.rules到/etc/udev/rules.d并刷新udev规则。

  4. 运行脚本k3.sh，连接失败；运行其他k3-xxx.sh脚本，现象一样。
    报错log如下（两次区别是一次连了J-Link的Vref脚，一次没连，结果都是失败）：

> test@test-ZhaoYang-X5-14-IRL:~/K3/spacemit-openocd-linux-V1.1.2/bin$ ./k3.sh
> 
> Open On-Chip Debugger 0.12.0+dev-g57f52fa (2026-06-10-07:54)
> 
> Licensed under GNU GPL v2
> 
> For bug reports, read
> 
> http://openocd.org/doc/doxygen/bugs.html
> 
> 8000
> 
> 0
> 
> acpu
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0
> 
> 0
> 
> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 
> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 
> 0 1 2 3
> 
> sbawrite32
> 
> Info : [k3.x100.0] Hardware thread awareness created
> 
> Info : [k3.x100.4] Hardware thread awareness created
> 
> Info : [k3.a100.8] Hardware thread awareness created
> 
> Info : [k3.a100.12] Hardware thread awareness created
> 
> Info : J-Link Pro V4 compiled Sep 22 2029 15:00:37
> 
> Info : Hardware version: 11.00
> 
> Info : VTarget = 3.260 V
> 
> Info : clock speed 2000 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: post.unknown: IR capture error; saw 0x1ff not 0x1
> 
> Warn : Bypassing JTAG setup events due to errors
> 
> Info : [k3.x100.0] starting gdb server on 1024
> 
> Info : Listening on port 1024 for gdb connections
> 
> Error: [k3.x100.0] set_group is not implemented for this target.
> 
> scripts/spacemit-k3.cfg:145: Error:
> 
> Traceback (most recent call last):
> 
> File "scripts/spacemit-k3.cfg", line 145, in script
> 
> {k3.x100.0 riscv set_group} halt_group 0 trigger 0
> 
> Error: [k3.x100.0] Unsupported DTM version: -1
> 
> Error: [k3.x100.0] Could not identify target type.
> 
> Error: [k3.x100.1] Unsupported DTM version: -1
> 
> Error: [k3.x100.1] Could not identify target type.
> 
> Error: [k3.x100.2] Unsupported DTM version: -1
> 
> Error: [k3.x100.2] Could not identify target type.
> 
> Error: [k3.x100.3] Unsupported DTM version: -1
> 
> Error: [k3.x100.3] Could not identify target type.
> 
> Error: [k3.x100.4] Unsupported DTM version: -1
> 
> Error: [k3.x100.4] Could not identify target type.
> 
> Error: [k3.x100.5] Unsupported DTM version: -1
> 
> Error: [k3.x100.5] Could not identify target type.
> 
> Error: [k3.x100.6] Unsupported DTM version: -1
> 
> Error: [k3.x100.6] Could not identify target type.
> 
> Error: [k3.x100.7] Unsupported DTM version: -1
> 
> Error: [k3.x100.7] Could not identify target type.
> 
> Error: [k3.a100.8] Unsupported DTM version: -1
> 
> Error: [k3.a100.8] Could not identify target type.
> 
> Error: [k3.a100.9] Unsupported DTM version: -1
> 
> Error: [k3.a100.9] Could not identify target type.
> 
> Error: [k3.a100.10] Unsupported DTM version: -1
> 
> Error: [k3.a100.10] Could not identify target type.
> 
> Error: [k3.a100.11] Unsupported DTM version: -1
> 
> Error: [k3.a100.11] Could not identify target type.
> 
> Error: [k3.a100.12] Unsupported DTM version: -1
> 
> Error: [k3.a100.12] Could not identify target type.
> 
> Error: [k3.a100.13] Unsupported DTM version: -1
> 
> Error: [k3.a100.13] Could not identify target type.
> 
> Error: [k3.a100.14] Unsupported DTM version: -1
> 
> Error: [k3.a100.14] Could not identify target type.
> 
> Error: [k3.a100.15] Unsupported DTM version: -1
> 
> Error: [k3.a100.15] Could not identify target type.
> 
> test@test-ZhaoYang-X5-14-IRL:~/K3/spacemit-openocd-linux-V1.1.2/bin$ ./k3.sh
> 
> Open On-Chip Debugger 0.12.0+dev-g57f52fa (2026-06-10-07:54)
> 
> Licensed under GNU GPL v2
> 
> For bug reports, read
> 
> http://openocd.org/doc/doxygen/bugs.html
> 
> 8000
> 
> 0
> 
> acpu
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0 1 2 3
> 
> 0
> 
> 0
> 
> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 
> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 
> 0 1 2 3
> 
> sbawrite32
> 
> Info : [k3.x100.0] Hardware thread awareness created
> 
> Info : [k3.x100.4] Hardware thread awareness created
> 
> Info : [k3.a100.8] Hardware thread awareness created
> 
> Info : [k3.a100.12] Hardware thread awareness created
> 
> Info : J-Link Pro V4 compiled Sep 22 2029 15:00:37
> 
> Info : Hardware version: 11.00
> 
> Info : VTarget = 0.000 V
> 
> Info : clock speed 2000 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: post.unknown: IR capture error; saw 0x1ff not 0x1
> 
> Warn : Bypassing JTAG setup events due to errors
> 
> Info : [k3.x100.0] starting gdb server on 1024
> 
> Info : Listening on port 1024 for gdb connections
> 
> Error: [k3.x100.0] set_group is not implemented for this target.
> 
> scripts/spacemit-k3.cfg:145: Error:
> 
> Traceback (most recent call last):
> 
> File "scripts/spacemit-k3.cfg", line 145, in script
> 
> {k3.x100.0 riscv set_group} halt_group 0 trigger 0
> 
> Error: [k3.x100.0] Unsupported DTM version: -1
> 
> Error: [k3.x100.0] Could not identify target type.
> 
> Error: [k3.x100.1] Unsupported DTM version: -1
> 
> Error: [k3.x100.1] Could not identify target type.
> 
> Error: [k3.x100.2] Unsupported DTM version: -1
> 
> Error: [k3.x100.2] Could not identify target type.
> 
> Error: [k3.x100.3] Unsupported DTM version: -1
> 
> Error: [k3.x100.3] Could not identify target type.
> 
> Error: [k3.x100.4] Unsupported DTM version: -1
> 
> Error: [k3.x100.4] Could not identify target type.
> 
> Error: [k3.x100.5] Unsupported DTM version: -1
> 
> Error: [k3.x100.5] Could not identify target type.
> 
> Error: [k3.x100.6] Unsupported DTM version: -1
> 
> Error: [k3.x100.6] Could not identify target type.
> 
> Error: [k3.x100.7] Unsupported DTM version: -1
> 
> Error: [k3.x100.7] Could not identify target type.
> 
> Error: [k3.a100.8] Unsupported DTM version: -1
> 
> Error: [k3.a100.8] Could not identify target type.
> 
> Error: [k3.a100.9] Unsupported DTM version: -1
> 
> Error: [k3.a100.9] Could not identify target type.
> 
> Error: [k3.a100.10] Unsupported DTM version: -1
> 
> Error: [k3.a100.10] Could not identify target type.
> 
> Error: [k3.a100.11] Unsupported DTM version: -1
> 
> Error: [k3.a100.11] Could not identify target type.
> 
> Error: [k3.a100.12] Unsupported DTM version: -1
> 
> Error: [k3.a100.12] Could not identify target type.
> 
> Error: [k3.a100.13] Unsupported DTM version: -1
> 
> Error: [k3.a100.13] Could not identify target type.
> 
> Error: [k3.a100.14] Unsupported DTM version: -1
> 
> Error: [k3.a100.14] Could not identify target type.
> 
> Error: [k3.a100.15] Unsupported DTM version: -1
> 
> Error: [k3.a100.15] Could not identify target type.
  1. 我把测试环境拍了几张照片，请各位大佬帮忙检查一下。

整体环境

jtag_test
jtag_test1920×2560 553 KB

用飞线连接板端Pri JTAG

JTAG_BOARD
JTAG_BOARD1920×2560 307 KB

J-Link的GND和板端UART的GND连接

JTAG_GND
JTAG_GND1920×2560 214 KB

J-Link端连线（角度1）

JLINK_1
JLINK_11920×1440 122 KB

J-Link端连线（角度2）

JLINK_2
JLINK_21920×2560 195 KB

2

看你的接线好像没问题，板子应该上电了吧

我这边是可以的：

img_v3_0212t_85ad9390-984b-4d04-8825-cd74eb52457g
img_v3_0212t_85ad9390-984b-4d04-8825-cd74eb52457g1920×1080 138 KB

img_v3_0212t_331c0bcb-a32f-45c3-b18a-cf91355f5cag
img_v3_0212t_331c0bcb-a32f-45c3-b18a-cf91355f5cag1920×1080 226 KB

liangzhen@liangzhen-ubuntu:~/workspace/spacemit-openocd-linux-V1.1.2/bin$ ./k3.sh 

Open On-Chip Debugger 0.12.0+dev-g57f52fa (2026-06-10-07:54)

Licensed under GNU GPL v2

For bug reports, read

	http://openocd.org/doc/doxygen/bugs.html

8000

0

acpu

0 1 2 3

0 1 2 3

0 1 2 3

0 1 2 3

0 1 2 3

0

0

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

0 1 2 3

sbawrite32

Info : [k3.x100.0] Hardware thread awareness created

Info : [k3.x100.4] Hardware thread awareness created

Info : [k3.a100.8] Hardware thread awareness created

Info : [k3.a100.12] Hardware thread awareness created

Info : J-Link V9 compiled May  7 2021 16:26:12

Info : Hardware version: 9.40

Info : VTarget = 3.266 V

Info : clock speed 2000 kHz

Info : JTAG tap: post.unknown tap/device found: 0x08502c0d (mfg: 0x606 (Shenzhen Chixingzhe Technology Co Ltd), part: 0x8502, ver: 0x0)

Info : JTAG tap: pre.unknown enabled

Info : JTAG tap: k3.cpu enabled

Info : [k3.x100.0] datacount=2 progbufsize=2

Info : [k3.x100.0] Vector support with vlenb=32

Info : [k3.x100.0] S?aia detected with IMSIC

Info : [k3.x100.0] Core 0 made part of halt group 1.

Info : [k3.x100.0] Examined RISC-V core

Info : [k3.x100.0]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.0] Examination succeed

Info : [k3.x100.1] datacount=2 progbufsize=2

Info : [k3.x100.1] Vector support with vlenb=32

Info : [k3.x100.1] S?aia detected with IMSIC

Info : [k3.x100.1] Core 1 made part of halt group 1.

Info : [k3.x100.1] Examined RISC-V core

Info : [k3.x100.1]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.1] Examination succeed

Info : [k3.x100.2] datacount=2 progbufsize=2

Info : [k3.x100.2] Vector support with vlenb=32

Info : [k3.x100.2] S?aia detected with IMSIC

Info : [k3.x100.2] Core 2 made part of halt group 1.

Info : [k3.x100.2] Examined RISC-V core

Info : [k3.x100.2]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.2] Examination succeed

Info : [k3.x100.3] datacount=2 progbufsize=2

Info : [k3.x100.3] Vector support with vlenb=32

Info : [k3.x100.3] S?aia detected with IMSIC

Info : [k3.x100.3] Core 3 made part of halt group 1.

Info : [k3.x100.3] Examined RISC-V core

Info : [k3.x100.3]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.3] Examination succeed

Info : [k3.x100.4] datacount=2 progbufsize=2

Info : [k3.x100.4] Vector support with vlenb=32

Info : [k3.x100.4] S?aia detected with IMSIC

Info : [k3.x100.4] Core 0 made part of halt group 1.

Info : [k3.x100.4] Examined RISC-V core

Info : [k3.x100.4]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.4] Examination succeed

Info : [k3.x100.5] datacount=2 progbufsize=2

Info : [k3.x100.5] Vector support with vlenb=32

Info : [k3.x100.5] S?aia detected with IMSIC

Info : [k3.x100.5] Core 1 made part of halt group 1.

Info : [k3.x100.5] Examined RISC-V core

Info : [k3.x100.5]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.5] Examination succeed

Info : [k3.x100.6] datacount=2 progbufsize=2

Info : [k3.x100.6] Vector support with vlenb=32

Info : [k3.x100.6] S?aia detected with IMSIC

Info : [k3.x100.6] Core 2 made part of halt group 1.

Info : [k3.x100.6] Examined RISC-V core

Info : [k3.x100.6]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.6] Examination succeed

Info : [k3.x100.7] datacount=2 progbufsize=2

Info : [k3.x100.7] Vector support with vlenb=32

Info : [k3.x100.7] S?aia detected with IMSIC

Info : [k3.x100.7] Core 3 made part of halt group 1.

Info : [k3.x100.7] Examined RISC-V core

Info : [k3.x100.7]  XLEN=64, misa=0x8000000000b411af

Info : [k3.x100.7] Examination succeed

Info : [k3.a100.8] datacount=2 progbufsize=2

Info : [k3.a100.8] Vector support with vlenb=128

Info : [k3.a100.8] S?aia detected with IMSIC

Info : [k3.a100.8] Core 0 made part of halt group 1.

Info : [k3.a100.8] Examined RISC-V core

Info : [k3.a100.8]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.8] Examination succeed

Info : [k3.a100.9] datacount=2 progbufsize=2

Info : [k3.a100.9] Vector support with vlenb=128

Info : [k3.a100.9] S?aia detected with IMSIC

Info : [k3.a100.9] Core 1 made part of halt group 1.

Info : [k3.a100.9] Examined RISC-V core

Info : [k3.a100.9]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.9] Examination succeed

Info : [k3.a100.10] datacount=2 progbufsize=2

Info : [k3.a100.10] Vector support with vlenb=128

Info : [k3.a100.10] S?aia detected with IMSIC

Info : [k3.a100.10] Core 2 made part of halt group 1.

Info : [k3.a100.10] Examined RISC-V core

Info : [k3.a100.10]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.10] Examination succeed

Info : [k3.a100.11] datacount=2 progbufsize=2

Info : [k3.a100.11] Vector support with vlenb=128

Info : [k3.a100.11] S?aia detected with IMSIC

Info : [k3.a100.11] Core 3 made part of halt group 1.

Info : [k3.a100.11] Examined RISC-V core

Info : [k3.a100.11]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.11] Examination succeed

Info : [k3.a100.12] datacount=2 progbufsize=2

Info : [k3.a100.12] Vector support with vlenb=128

Info : [k3.a100.12] S?aia detected with IMSIC

Info : [k3.a100.12] Core 0 made part of halt group 1.

Info : [k3.a100.12] Examined RISC-V core

Info : [k3.a100.12]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.12] Examination succeed

Info : [k3.a100.13] datacount=2 progbufsize=2

Info : [k3.a100.13] Vector support with vlenb=128

Info : [k3.a100.13] S?aia detected with IMSIC

Info : [k3.a100.13] Core 1 made part of halt group 1.

Info : [k3.a100.13] Examined RISC-V core

Info : [k3.a100.13]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.13] Examination succeed

Info : [k3.a100.14] datacount=2 progbufsize=2

Info : [k3.a100.14] Vector support with vlenb=128

Info : [k3.a100.14] S?aia detected with IMSIC

Info : [k3.a100.14] Core 2 made part of halt group 1.

Info : [k3.a100.14] Examined RISC-V core

Info : [k3.a100.14]  XLEN=64, misa=0x8000000000b4112f

Info : [k3.a100.14] Examination succeed

Info : [k3.a100.15] datacount=2 progbufsize=2

Info : [k3.a100.15] Vector support with vlenb=128

Info : [k3.a100.15] S?aia detected with IMSIC

Info : [k3.a100.15] Core 3 made part of halt group 1.

Info : [k3.a100.15] Examined RISC-V core

Info : [k3.a100.15]  XLEN=64, misa=0x8000000000b4112f

adapter speed: 8000 kHz

    TargetName         Type       Endian TapName            State       

--  ------------------ ---------- ------ ------------------ ------------

 0  k3.x100.0          riscv      little k3.cpu             running

 1  k3.x100.1          riscv      little k3.cpu             running

 2  k3.x100.2          riscv      little k3.cpu             running

 3  k3.x100.3          riscv      little k3.cpu             running

 4  k3.x100.4          riscv      little k3.cpu             running

 5  k3.x100.5          riscv      little k3.cpu             running

 6  k3.x100.6          riscv      little k3.cpu             running

 7  k3.x100.7          riscv      little k3.cpu             running

 8  k3.a100.8          riscv      little k3.cpu             running

 9  k3.a100.9          riscv      little k3.cpu             running

10  k3.a100.10         riscv      little k3.cpu             running

11  k3.a100.11         riscv      little k3.cpu             running

12  k3.a100.12         riscv      little k3.cpu             running

13  k3.a100.13         riscv      little k3.cpu             running

14  k3.a100.14         riscv      little k3.cpu             running

15* k3.a100.15         riscv      little k3.cpu             running

Info : [k3.a100.15] Examination succeed

Info : [k3.x100.0] starting gdb server on 1024

Info : Listening on port 1024 for gdb connections

Info : [k3.x100.0] External trigger 0 made part of halt group 0.

Info : [k3.x100.4] External trigger 0 made part of halt group 0.

Info : [k3.a100.8] External trigger 0 made part of halt group 0.

Info : [k3.a100.12] External trigger 0 made part of halt group 0.

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections
3

我看你一共连了5根信号线和1根GND共6根线，Vref不用连接吗，但我看你log打印VTarget = 3.266 V。我不连的话VTarget = 0 V。
另外J-Link里面跳线帽拔掉了吧？

4

跳线帽没拔，使用J-Link 内部供电，应该和Vref通过板子供电一样。

5

谢谢。
我检查了硬件应该没什么问题。
JTAG的GPIO复用功能需要单独配置吗，我现在是uboot起来之后进入系统了。

6

这个类型的板子不用的