AlainD

I was thinking if there where changes after the code "change". Depends on the usage if it's a problem.

Difficult question : are the numbers really random? Off course all zeroes is the worst...

Oh I have to read more carefully. Does it need the extra pins right next (before) the sdcard holder? Those are non standard with a 4.1 with pins.

"New orders are expected to be fulfilled around mid-June, 2025."

Thanks learned something. A very useful tool also, but not available at the moment.

Maybe I should install the pico 2 toolchain.

This is quite normal. Coremark will probably run inside the core's cache and thus only use the core itself. You're test is probably using the memory and this is shared.

Thanks. I could have thought it with the TCM memory.

Big difference between 528 and 600 Mhz. Has anybody nr's for 528Mhz? And single core RP2350?

For me the "teensy" specific thing is the quality software eco-system. A RP2350A (or RP2354A + extra flash) Teensy (read here designed by Paul), would do most things that I need.

So the 2.0,LC,3.2,3.5 and 3.6 are not Teensy-Compatible...

Both single core and multicore are important. Although -if I read the comments correct- the code doesn't seems to check memory access much. Most current code will be single core and need to be adapted for multi core. It's nice to know how...

For me it's not about speed, but the software ecosystem. rp2350 will be fast enough.

Sad story. I fear that this gives less sellers in the EU and thus more difficult to get a teensy with some other stuff. A Teensy alone and thus with shipping, will be a lot more expensive.