Link from post #7 p.96 indicates pull-up and pull-down of 40K nominal. Although I can't find the post just yet, there was a suggestion to set to a known state. Still searching. The other idea was to use getPinMode() to see what the defaults are at start-up and see if they remain in that state.
Regarding the code snippet, ref L9 I've had issues with timers running after cut-n-paste into the Lefthand console side of the WebIDE, under the assumption they were cleared. From another post I use the following to see if any are running:
console.log(global["\xFF"].timers); //nice, less info
trace(global["\xFF"].timers); //full info
It might be that constantly pressing the button creates a new timer instance L9, leaving the previous there in memory. Should that be the case, code might be running not allowing the deep sleep state to occur. Just a guess, but worth checking.
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.
Sun 2020.03.01
Link from post #7 p.96 indicates pull-up and pull-down of 40K nominal. Although I can't find the post just yet, there was a suggestion to set to a known state. Still searching. The other idea was to use getPinMode() to see what the defaults are at start-up and see if they remain in that state.
Regarding the code snippet, ref L9 I've had issues with timers running after cut-n-paste into the Lefthand console side of the WebIDE, under the assumption they were cleared. From another post I use the following to see if any are running:
It might be that constantly pressing the button creates a new timer instance L9, leaving the previous there in memory. Should that be the case, code might be running not allowing the deep sleep state to occur. Just a guess, but worth checking.