 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Pico W bricked?
| Author | Message | ||||
| jovian Regular Member  Joined: 16/04/2017 Location: AustraliaPosts: 62 |
Hello all Here we go again.... My project was coming on swimmingly - actually incredibly frustratingly if I'm honest - until I had the need to OPTION RESET ALL. I intended to restore my overclocked 378k speed but in error I typed OPTION CPUSPEED 374000. The Pico went on holiday and has not since returned. I tried reinstalling the firmware but no success. The drive appears on the desktop and I can successfully drag and copy to it... it *appears* to install but no heartbeat LED on power up. It has about a million connections soldered to it all heatshrinked and ticketty boo in a lovely case, I'd jump start it if I could. Anyone had this? Any fixes? Thanks in advance, Joe |
||||
disco4now Guru  Joined: 18/12/2014 Location: AustraliaPosts: 896 |
Have you loaded the clear_flash.uf2 firmware. Then try the firmware again. If you just reload the same firmware then MMBasic will come up with its same settings as when it died. Latest F4 Latest H7 |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9307 |
I thought the latest versions of the PM or PM_VGA automatically performed a clear_flash procedure before installing the new FW? Pretty sure I read that somewhere.... Peter? If that is the case, you might need to wait a little while AFTER uploading the new FW file, before the on-board LED starts blinking, as it will take a few seconds for the FW to clear the flash first, then setup a new copy of the FW - then the LED will start blinking. How long did you wait? Normal startup takes about six seconds for the PM to load various bits of the FW into the RAM and start the interpreter. With clear_flash added into the mix, it could be the best part of ten seconds or so, before the LED starts blinking. This longer then usual delay will only be on the first boot-up since uploading the new copy of the FW. Subsequent start-ups should revert back to the more normal six seconds or so. Just a thought. Smoke makes things work. When the smoke gets out, it stops! |
||||
phil99 Guru Joined: 11/02/2018 Location: AustraliaPosts: 2135 |
Bound to be corrected on this but the automatic clear_flash only seems to apply when there has been a significant change in the firmware that affects how tokens are interpreted or how flash is allocated. |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9307 |
Oh, right! THAT must have been what I read - sorry everyone. Smoke makes things work. When the smoke gets out, it stops! |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 3802 |
Any time things are wacky, it has to be worth trying clear_flash.uf2 John |
||||
| PhenixRising Guru Joined: 07/11/2023 Location: United KingdomPosts: 864 |
Not at all. Had you not posted, I for one wouldn't have known  |
||||
| jovian Regular Member Joined: 16/04/2017 Location: AustraliaPosts: 62 |
Hi all Thanks for your responses. I received no notification for some reason so I thought you were all fed up with me! I just solved it! I'm so happy I don't have to desolder everything and start again. The file is called flash_nuke.uf2 and it magically revived the Pico W, simply by dragging it in to the folder on bootsel startup. Cheers J |
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 6795 |
It works. :) It basically turns your device back into a new Pico. Coincidentally, I've just used it before replacing MMBasic with Circuit Python on one. Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
 Print this page |
