That is strange. So that's exactly the same wiring you had when running the version checking code?
You do seem to have some saved code though - could you try typing reset() followed by save() on the left-hand side, and then trying upload again?
I guess it's possible that the ESP8266 was already powered up by the saved code, and the combination of turning it off for a split second for the reset and then powering it back on caused some kind of problems.
Sorry to hear about your Pico - what revision is the PCB on it (it should be printed on the back I think)? The later ones have a self-resetting fuse so even if you short ground and VCC you're very unlikely to cause any damage.
One other thing - could you add wifi.at.debug() right after your existing code - so:
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.
That is strange. So that's exactly the same wiring you had when running the version checking code?
You do seem to have some saved code though - could you try typing
reset()
followed bysave()
on the left-hand side, and then trying upload again?I guess it's possible that the ESP8266 was already powered up by the saved code, and the combination of turning it off for a split second for the reset and then powering it back on caused some kind of problems.
Sorry to hear about your Pico - what revision is the PCB on it (it should be printed on the back I think)? The later ones have a self-resetting fuse so even if you short ground and VCC you're very unlikely to cause any damage.
One other thing - could you add
wifi.at.debug()
right after your existing code - so:and post up what gets printed out? It might help I guess.