Not entirely sure what you're saying, as Micropython on Zephyr exists. https://docs.micropython.org/en/latest/zephyr/quickref.html https://docs.micropython.org

Not entirely sure what you're saying, as Micropython on Zephyr exists. https://docs.micropython.org/en/latest/zephyr/quickref.html https://docs.micropython.org/en/latest/zephyr/quickref.html Very weird seeing the Zephyr booting message I've seen so many times followed by the micropython repl startup message I've seen so many times. Hard to think of a good app for that topology. In the sense that I could stick circuitpython or micropython on a ESP32, or zephyr on a ESP32, so an app running both would get me ... ? Conceptually, the *python people "could in theory" give up on porting to infinite number of new boards and focus really hard on working under Zephyr, and let Zephyr worry about porting to infinite number of new boards. The idea of upgrading my MicroPython under Zephyr under MCUboot under Eclipse hawkBit over the wifi is pretty intriguing sounding challenge. I have not dug into this technology stack other than recreationally. I'm a little unclear how interop works beyond the existing example of passing simple hardware pins thru. For example if MicroPython had a library that interop directly with the Zephyr RTOS features, that would be quite handy. Another thing I notice is the interop in the docs is simple pin pass thru, hard to even imagine how Zephyr's wide variety of networking stacks would pass thru for Python to use. It looks like there is nothing developed at this point where the uC could run a RTOS thread to "do stuff" while a MicroPython thread handled a wifi UI or UI in general or handled the non-RTOS tasks, although that would be cool.