A late update after already 2 month and the new firmware update.
I never saw the MEMORY_BUSY message since then, and for the connection same thing, it may have happened only once or twice for 12 ish connections.
I assume that 2v15 fixed a lot of what was happening from the start, that it did not reappear in 2v16, and that the main culprit for the connection is only windows and the bluetooth drivers.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
A late update after already 2 month and the new firmware update.
I never saw the MEMORY_BUSY message since then, and for the connection same thing, it may have happened only once or twice for 12 ish connections.
I assume that 2v15 fixed a lot of what was happening from the start, that it did not reappear in 2v16, and that the main culprit for the connection is only windows and the bluetooth drivers.
Thanks for all your work! ❤