General • Re: Did I break my original Pico by loading Pico 2 programs into it?

That's correct and worked when I tested it. The target chip should ignore everything which isn't intended for it

Maybe it is a new feature or rp2350 ROM and works only in one way? Pico 2 ignores Pico 1 but not the other way?

Not that I can imagine. The BOOT ROM Loader should be checking the Family ID in each UF2 block and ignoring those it doesn't recognise.

The RP2040 only recognises it's own Family ID, will reject RP235X and anything else.

The RP235X has a set of Family ID but rejects everything else, so will reject RP2040 UF2 by default. I believe that could get screwed with, and cause all sorts of weird things to happen, even bricking an RP235X, but that's apparently not something to worry about and we are talking of loading to an RP2040.

How could one otherwise flash Pico 2 Doom to version 1?

You can't (*).

You have to build an RP2040 version UF2 and a separate RP235X UF2, then load the appropriate UF2 to the hardware it was compiled for.

(*) You can however concatenate those two UF2 to create a single 'Universal UF2' which will load to either RP2040 or RP235X. Each will ignore the blocks intended for the other.

It is possible the OP built for RP2040, built for RP235X, built for RP2040 again, but has got something different to the last time through ''cmake' caching or similar. It's always best to clear out build directories and start again if changing build options.

But pre-built UF2 for the RP2040 should still be the same as they ever were, should run the same on any RP2040.

Statistics: Posted by hippy — Wed Nov 13, 2024 10:43 am

---