Technology

34886 readers

30 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

MinutePhrase@lemmy.ml

Introducing Raspberry Pi Pico 2 (www.raspberrypi.com)

submitted 3 months ago by user68k@wired.bluemarch.art to c/technology@lemmy.ml

10 comments fedilink hide all child comments

We’re happy to announce the launch of Raspberry Pi Pico 2, our second-generation microcontroller board, built on RP2350: a new high-performance, secure microcontroller designed here at Raspberry Pi.

With a higher core clock speed, twice the memory, more powerful Arm cores, new security features, and upgraded interfacing capabilities, Pico 2 delivers a significant performance and feature uplift, while retaining hardware and software compatibility with earlier members of the Pico series.

Pico 2 is on sale now, priced at $5.

you are viewing a single comment's thread
view the rest of the comments

[–] baduhai@sopuli.xyz 3 points 3 months ago (1 children)

That's correct.

the boot keys are burned into OTP memory so they can't be erased or changed

Which is good, as otherwise it would defeat the purpose of secure boot.

[–] CalcProgrammer1@lemmy.ml 5 points 3 months ago* (last edited 3 months ago)

I wish these implementations of secure boot were designed more to protect the SOFTWARE against "theft" than the HARDWARE against "tampering". Let us wipe the secure boot keys, but in the process erase the firmware (or have the firmware encrypted so that erasing the keys renders it unbootable) and then allow new code to run. Blocking third party firmware on consumer devices is a shit move. It just creates more e-waste when the OEM stops updating it and the community can't make their own replacement firmware.