It could be you are (or have) uploaded some code to Espruino that causes it to crash - it's all I can think that would cause Putty to stop responding. Definitely I2C can block for a few seconds if the device on the end isn't responding.
The BTN+RST thing you did only works temporarily - so if you unplugged/replugged or reset Espruino then it'd spring back up exactly as it was before. To fix that, I'd do the BTN+RST thing, connect with Putty/Web IDE and type save().
Of course maybe the simplest solution is just to re-flash the firmware? On the Espruino board (at least as long as you're not using @DrAzzy's BigRam builds) that'll clear out any saved code.
Also, it might be worth trying another USB cable. Sounds crazy but so many people have had problems with them that it wouldn't surprise me.
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.
It could be you are (or have) uploaded some code to Espruino that causes it to crash - it's all I can think that would cause Putty to stop responding. Definitely I2C can block for a few seconds if the device on the end isn't responding.
The BTN+RST thing you did only works temporarily - so if you unplugged/replugged or reset Espruino then it'd spring back up exactly as it was before. To fix that, I'd do the BTN+RST thing, connect with Putty/Web IDE and type
save()
.Of course maybe the simplest solution is just to re-flash the firmware? On the Espruino board (at least as long as you're not using @DrAzzy's BigRam builds) that'll clear out any saved code.
Also, it might be worth trying another USB cable. Sounds crazy but so many people have had problems with them that it wouldn't surprise me.