dt-BL10 with bl602 (risc-v)

[ntn888]

board: https://github.com/SmartArduino/Doiting_BL
bl602 soc: https://github.com/bouffalolab/bl_mcu_sdk/

using https://github.com/UweBonnes/blackmagic/tree/ruabmbua
compiled for hosted..
output

./src/blackmagic -t
BMP hosted (BMP Only) v1.6.1-977-g5d40c88-dirty
Using:
 Black Magic Probe (SWLINK) v1.6.1-977-g5d40c88-dirty E4D16EE5
Running in Test Mode
Target voltage:  Volt
Speed set to  3.2727 MHz for SWD
Trying old JTAG to SWD sequence
No usable DP found
Scan SWD failed, trying JTAG!
Speed set to  3.2727 MHz for JTAG
 1: IDCODE: 0x20000c05, IR len 5 RVDBG013
RISC-V DTM id 0x20000c05 detected: `RVDBG013`
Scanning RISC-V target ...
  dtmcs = 0x00005071
  debug version = 0.13
  abits = 7
  idle = stay 4 cycles in run/test
Supports set/clear-resethaltreq
datacount = 1
RISC-V: Program buffer with available size 2 supported.
hartsellen = 0
num_harts = 1
RISC-V abstract command 0x00220301 not supported
RISC-V abstract command error: 2
Read MISA failed
RISC-V abstract command 0x00220f11 not supported
RISC-V abstract command error: 2
Read machine failed
RISC-V abstract command 0x002207b0 not supported
RISC-V abstract command error: 2
Read DCSR failed
RISC-V abstract command 0x002207a0 not supported
RISC-V abstract command error: 2
RISC-V abstract command 0x002307a0 not supported
RISC-V abstract command error: 2
RISC-V abstract command 0x002207a0 not supported
RISC-V abstract command error: 2
RISC-V abstract command 0x002307a0 not supported
RISC-V abstract command error: 2
Found 0 triggers
RISC-V abstract command 0x002207b0 not supported
RISC-V abstract command error: 2
Halt_resume read DCSR failed
***  1      RVDBG013 Generic RVDBG 0.13
RISC-V abstract command 0x002207b0 not supported
RISC-V abstract command error: 2
Halt_resume read DCSR failed

[dragonmux]

The scan situation for this board should be improved since #1683 (System Bus support) and #1924 (progbuf based CSR access support). Please let us know what a scan of this part looks like with the latest main.

Hopefully with those things resolved, you should see a lot less not supported/error and possibly even the necessary IDs to look at writing custom target handling for this part. This will be bumped into v2.1 due to the closeness to the v2.0 full release.