This Pico won't run your '.UF2' files which run on the other three, but does run the MicroPython and CircuitPython '.UF2' files.
The latter would indicate that BOOTSEL, Flash, RAM, everything else, is working as expected, and if those run, so too should your own '.UF2', and they do on the other three.
So it seems the issue is your '.UF2' on that particular Pico which is problematic.
So what could make your '.UF2' incompatible with that Pico, what's different between your '.UF2' and MicroPython and CircuitPython, and/or what's different about that particular Pico ?
My clutching at straw guesses would be that the RP2040 chip is different, has different stepping, or the Flash chip is somehow different, maybe the crystal, that allows the '.UF2' boot-up the other three but not this one.
It could be a new board revision, some short on the board, a power supply or USB issue, could perhaps be an OS issue, but hard to see how any of that would affect only your '.UF2' and not MicroPython or CircuitPython.
You could grab a magnifying glass and see if you can see any difference. You could also look at what 'dmesg' shows when the good and bad Pico show when plugged into USB, and after you have loaded your '.UF2'.
I would suggest using 'picotool' to upload the '.UF2' to this Pico to see if that reports anything out of the ordinary.
I would also suggest building a 'LED blink' which is Run from RAM to see if that works, having checked it does on the others.
It is, as you say, a strange issue; very strange.
The latter would indicate that BOOTSEL, Flash, RAM, everything else, is working as expected, and if those run, so too should your own '.UF2', and they do on the other three.
So it seems the issue is your '.UF2' on that particular Pico which is problematic.
So what could make your '.UF2' incompatible with that Pico, what's different between your '.UF2' and MicroPython and CircuitPython, and/or what's different about that particular Pico ?
My clutching at straw guesses would be that the RP2040 chip is different, has different stepping, or the Flash chip is somehow different, maybe the crystal, that allows the '.UF2' boot-up the other three but not this one.
It could be a new board revision, some short on the board, a power supply or USB issue, could perhaps be an OS issue, but hard to see how any of that would affect only your '.UF2' and not MicroPython or CircuitPython.
You could grab a magnifying glass and see if you can see any difference. You could also look at what 'dmesg' shows when the good and bad Pico show when plugged into USB, and after you have loaded your '.UF2'.
I would suggest using 'picotool' to upload the '.UF2' to this Pico to see if that reports anything out of the ordinary.
I would also suggest building a 'LED blink' which is Run from RAM to see if that works, having checked it does on the others.
It is, as you say, a strange issue; very strange.
Statistics: Posted by hippy — Fri Mar 29, 2024 11:21 am
