J-Link connect error

Using a (cheap) J-Link V9, buy from Taobao. upgraded firmware to V6.54a

connect wires to longan nano, correctly.

and then, use J-Flash to connect it, selected jtag, 4000kHz
report error:

Connecting …

  • Connecting via USB to J-Link device 0
  • J-Link firmware: J-Link V9 compiled May 17 2019 09:50:41
  • Device “GD32VF103CBT6” selected.
  • Target interface speed: 4000 kHz (Fixed)
  • VTarget = 3.287V
  • ConfigTargetSettings() start
  • ConfigTargetSettings() end
  • TotalIRLen = 10, IRPrint = 0x0021
  • JTAG chain detection found 2 devices:
  • #0 Id: 0x1000563D, IRLen: 05, RV32
  • #1 Id: 0x790007A3, IRLen: 05, Unknown device
  • Debug architecture:
  • RISC-V debug: 0.13
  • AddrBits: 7
  • DataBits: 32
  • IdleClks: 7
  • Memory access:
  • Via system bus: No
  • Via ProgBuf: Yes (2 ProgBuf entries)
  • DataBuf: 4 entries
  • autoexec[0] implemented: Yes
  • Detected: RV32 core
  • CSR access via abs. commands: No
  • ERROR: Failed to connect.
    Could not establish a connection to target.

and at last, pop up a windows:

The Connected J-Link does not support RISC-V via JTAG.
Please Get in touch with SEGGER (support_jlink@segger.com)

so, help, what can i do next?

use the latest JLINK from Segger.
JLink_Windows_V654c

no use. report error as the same.

Application log started

  • J-Flash V6.54c (J-Flash compiled Nov 7 2019 17:01:41)
  • JLinkARM.dll V6.54c (DLL compiled Nov 7 2019 17:01:02)
    Creating new project …
  • New project created successfully
    Connecting …
  • Connecting via USB to J-Link device 0
  • J-Link firmware: J-Link V9 compiled May 17 2019 09:50:41
  • Device “GD32VF103CBT6” selected.
  • Target interface speed: 4000 kHz (Fixed)
  • VTarget = 3.222V
  • ConfigTargetSettings() start
  • ConfigTargetSettings() end
  • TotalIRLen = 10, IRPrint = 0x0021
  • JTAG chain detection found 2 devices:
  • #0 Id: 0x1000563D, IRLen: 05, RV32
  • #1 Id: 0x790007A3, IRLen: 05, Unknown device
  • Debug architecture:
  • RISC-V debug: 0.13
  • AddrBits: 7
  • DataBits: 32
  • IdleClks: 7
  • Memory access:
  • Via system bus: No
  • Via ProgBuf: Yes (2 ProgBuf entries)
  • DataBuf: 4 entries
  • autoexec[0] implemented: Yes
  • Detected: RV32 core
  • CSR access via abs. commands: No

Ok - looks like your Jlink probe (may be a “JLink Base” or a clone) is using firmware 9.6
To test this run jlink and then type f (for firmware).
May be an update can help : run jlinkconfig , then try to update the firmware.

Contact segger - as suggested.

In the meantime use “Jlink EDU” or “Jlink EDU mini” (about 15-20$ ). This does work.