OrbTrace mini not recognized as a probe.

[ohunter]

I think it'd be nice to be able to use the OrbTrace Mini along with these utilities but that doesn't seem to be possible. I suspect this has to do with the way that find_bmp() is looking for the device. I have not tested this on windows so it might be possible that it is detected there without any issues.

[compuphase]

The utilities locate the probe on their VID:PID numbers. The OrbTrace Mini uses different numbers than the Black Magic Probe. So you are correct: find_bmp() does not locate the OrbTrace.

However, the utilities also use the GDB protocol and the monitor command strings to set up the debug probe. So it will only work if OrbTrace is (by and large) compatible with the Black Magic Probe.

I do not own an OrbTrace Mini, so I cannot check.

[ohunter]

The orbtrace mini is a compatible hosted probe that supports blackmagic yes.

[retif]

OrbTrace is CMSIS-DAP v1 and v2 compatible

It is possible to run Black Magic Debug App, which can connect to Orbtrace successfully.
To make it work we need to make change to bmp-scan.h

#define BMP_PORT_GDB      2000  /* TCP/IP port for gdbserver */

It is the only way to make BMDebug to go to 2000 instead of default 2159.
Would be great to be able to setup port in program argument though.

Black Magic Debug App also currently does not allow to change the port through argument.

$ blackmagic -v 5 -P 1
Black Magic Debug App v1.10.0-802-g15b1d4b0
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link and FTDI (MPSSE)
Using 1209:3443 326C708163008E06 Orbcode
 Orbtrace v1.3.1-0-gd096575
Using bulk transfer
CMSIS-DAP v2.1.0, Adaptor version v1.3.1-0-gd096575
Capabilities: 03 (JTAG/SWD)
Adaptor supports DAP SWD sequences
Setting V6ONLY to off for dual stack listening.
Listening on TCP port: 2000