pimoroni-pico icon indicating copy to clipboard operation
pimoroni-pico copied to clipboard

Pico doesnt run properly once main.py is saved on the board

Open davek61 opened this issue 4 years ago • 2 comments

Hello, I am using a pico display and it worked ok'ish until I saved my program on to the pico.

After this I have been unable to run programs from RAM. It keeps disconnecting or coming up with odd compile errors.

It was noticeably quite unreliable with regards to the USB serial connection even before this problem was observed. I often had to disconnect and reconnect before I could get the code to run in flash.

I an using the latest pimoroni python firmware downloaded today

davek61 avatar Mar 19 '21 17:03 davek61

Presumably this is because main.py is run at boot and trounces all the memory before you can get around to using it.

I've started avoiding saving as main.py for this reason, and it's still flaky :roll_eyes: - I don't think it helps that Thonny distinguishes between "Run" and "Stop -> Run" and if I fail to explicitly stop before each successive run of my code, it'll fall apart.

We're pretty much toe to toe with upstream MicroPython, though, so I'm guessing this is just a fact of life with MicroPython on Pico (exacerbated by the fact our products have big displays and allocate big display buffers) and I honestly don't think there's much we can do about it.

Gadgetoid avatar Mar 30 '21 11:03 Gadgetoid

@davek61 If your main.py is broken to the extent that it locks up your Pico and Thonny can't communicate with it any more to stop it, you can copy this file to it to clear the flash memory and start again. You'll need to copy the MicroPython firmware across again afterwards.

helgibbons avatar Mar 30 '21 12:03 helgibbons

Closing as stale/complete.

Gadgetoid avatar Mar 11 '24 13:03 Gadgetoid