Of the 3 devices I have, 1 doesn't disconnect after programming, but the other two do. Interestingly, the one that doesn't disconnect is running 2v05, and the two that do are running 2v04. Coincidence?
I don't think there is anything I have done to influence configuration/state on any of them. I have only run code from RAM. Maybe there is some bonding info or something client side where my Mac is doing something different for different devices based on history of how I have interacted with them.
Another difference occurred when I tried a Hard Reset to understand if there may be any state impacting behaviour (as described https://www.espruino.com/Pixl.js); interestingly the 2v04 devices do go through the process as described, but the 2v05 device just goes on to displaying "BOOTING" after the 10s.
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.
Some interesting extra findings:
Of the 3 devices I have, 1 doesn't disconnect after programming, but the other two do. Interestingly, the one that doesn't disconnect is running 2v05, and the two that do are running 2v04. Coincidence?
I don't think there is anything I have done to influence configuration/state on any of them. I have only run code from RAM. Maybe there is some bonding info or something client side where my Mac is doing something different for different devices based on history of how I have interacted with them.
Another difference occurred when I tried a Hard Reset to understand if there may be any state impacting behaviour (as described https://www.espruino.com/Pixl.js); interestingly the 2v04 devices do go through the process as described, but the 2v05 device just goes on to displaying "BOOTING" after the 10s.
Simon