Isn't the better way to interact with python embedded into gdb?

[ponyatov]

Modern gdb versions have --enable--python option which included Python interpreter into the debugger for any target processor/MCU. This option looks me much better to embed gdb interface into Jython, as we'll have a portable way to interact directly with hardware using any mainstream i/o interfaces like J-Link, ST-Link,.. or any UART/USB/ETH coupled with gdb stub on the device.

Factically, we can even write the firmware model without the use of any C code, as all MCU i/o mapped to a memory address space, and we need only small interrupt handling code and a sort of generic i/o gateway written in C.

[ponyatov]

Also, we can wrap cross-LLVM library built into Jupyter session, and play with dynamic compilation. It will be notable complex comparing to C programming, but Python can be used as a core for the interactive compiler by calling LLVM and rewriting parts of machine code on a hardware device.

[goatchurchprime]

Not sure I follow this.