GDB MI (remote) Adapter for OpenOCD Embedded Debugging

[anvol]

Binary Ninja currently lacks robust embedded debugging capabilities through GDB's Machine Interface (MI) protocol, particularly for OpenOCD-based targets. This gap limits dynamic analysis workflows for embedded firmware reverse engineering, where researchers need to:

• Debug ARM Cortex-M and other embedded microcontrollers directly within Binary Ninja
• Integrate with standard embedded debugging tools like OpenOCD
• Perform live memory inspection, breakpoint setting, and register analysis on real hardware
• Leverage Binary Ninja's powerful reverse engineering features during active debugging sessions

The current debugger support matrix shows GDB MI as an open issue (#170), indicating this is a recognized gap in the platform.

While #170 about local debugging, OpenOCD setup requires tar ext ip:port remote connection over tcp. Another option, like with Black Magic Probe, openocd is not required and GDB connects over USB CDC — tar ext /dev/cu.bmp-xxx