Hello,
exactly the same issue as in
Problems using JLink EDU with GD32VF103CBT6 based controller
but with Kendryte K210 mcu.
Display All
Is it EDU mini problem?
exactly the same issue as in
Problems using JLink EDU with GD32VF103CBT6 based controller
but with Kendryte K210 mcu.
Source Code
- JLink -device RISC-V -if JTAG -jtagconf -1,-1 -autoconnect 1 -speed 4000
- SEGGER J-Link Commander V6.56a (Compiled Nov 25 2019 17:06:23)
- DLL version V6.56a, compiled Nov 25 2019 17:05:33
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link EDU Mini V1 compiled Nov 12 2020 13:31:42
- Hardware version: V1.00
- S/N: 8010***
- License(s): FlashBP, GDB
- VTref=3.299V
- Device "RISC-V" selected.
- Connecting to target via JTAG
- ConfigTargetSettings() start
- ConfigTargetSettings() end
- TotalIRLen = 5, IRPrint = 0x01
- JTAG chain detection found 1 devices:
- #0 Id: 0x04E4796B, IRLen: 05, Unknown device
- Debug architecture:
- RISC-V debug: 0.11
- AddrBits: 5
- DataBits: 34
- IdleClks: 5
- ISA: RV32I+
- ****** Error: The connected J-Link does not support selecting another hart/core than 0 for RISC-V
- Specific core setup failed.
- Cannot connect to target.