Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST] Raspberry Pi RP2350 and Raspberry Pi Pico 2 support? #69

Closed
Hedda opened this issue Aug 9, 2024 · 5 comments
Closed

[REQUEST] Raspberry Pi RP2350 and Raspberry Pi Pico 2 support? #69

Hedda opened this issue Aug 9, 2024 · 5 comments

Comments

@Hedda
Copy link

Hedda commented Aug 9, 2024

Please consider looking into adding platform support for the new RP2350 MCU and the Raspberry Pi Pico 2 development board.

RP2350 is the successor and next-generation of RPi RP2040 so guess would need to update the RP2040 platform for it or add another platform?

RP2350 will be generally available in volume before the end of 2024. To register your interest, and to participate in the Raspberry Pi samples program, head over to the product page.

FYI, a "W" version of the Pico 2 with wireless support expected 'by the end of the year' according the people in the know 😛

Raspberry Pi team writes that the new RP2350 is vastly more sophisticated design than RP2040, however I understand it is supposedly backwards-compatible, though this new model now also offers faster resources, more IO/PIO, support for Arm TrustZone (security architecture), new HSTX peripheral for high-speed data transmission, and support for external QSPI PSRAM.

But I believe that the huge difference is otherwise the fact that the new Raspberry Pi RP2350 MCU features two-modes with dual-core RISC-V or dual-core ARM Cortex-M33 on the chip, meaning that you can either choose to run it in either RISC-V mode or in ARM Cortex-M3 mode, (but not more than two cores active at the same time, so "They're selectable at boot time: Each port into the bus fabric can be connected either to an M33 or a Hazard3 via a mux. You can even, if you're feeling obtuse, run with one of each." Arm/RISC-V switching is explained in the official datasheet:

Many RP2350-based development boards and products are apparently already in the pipeline:

https://www.raspberrypi.com/for-industry/powered-by/product-catalogue/?category=RP2350

If official Pico2 is hard to find then be ware that SparkFun Pro Micro RP2350 (and DEV-24870) and Adafruit Feather RP2350 (Product ID: 6000) are supposedly among the first of third-parties scheduled to become available to the first third-party boards available with RP2350:

This article from CNX software offers a little more insight into the RP2350 as compared to the RP2040:

"The RP2350 embeds both an open-source Hazard3 RISC-V dual-core CPU and a dual-core Cortex-M33, but only one cluster can be used at a given time. Apart from the faster MCU cores and higher SRAM capacity, the RP2350 is about the same as the RP2040, albeit it also adds one extra PIO block bringing the total to three. One important new feature is built-in security when using Arm Cortex-M33 cores with Trustzone and other security features."

As I understand it, the RP2350A package offers also the same pinout as the RP2040 microcontroller, but the company now also adding a larger RP2350B package with additional GPIOs and analog inputs.

Raspberry Pi used the same method as for the RP2040 to derive the RP2350 name. RP stands for “Raspberry Pi”, “2” is the number of cores, “3” refers to the MCU core used (e.g. Cortex-M33), and the last two numbers “4” and “0” use floor(log2(x/16k)) formula to calculate a number representing the SRAM and non-volatile storage capacity inside the chip.

image

image

image

image

image

PS: Off-topic; Raspberry Pi is btw offering a $10,000 bounty for first confirmed break of their new signed boot process on RP2350.:

https://github.com/raspberrypi/rp2350_hacking_challenge

"To get RP2350 hardware into the hands of the engineers most likely to find these flaws, we’ve partnered with the DEF CON hacking convention, which starts today in Las Vegas. This year’s badge is powered by RP2350, and makes a great platform for experimenting with our security architecture."

PPS: Ustream forum discussions from before when they leaked the news about this "Forthcoming RP235x" microcontroller:

@Hedda
Copy link
Author

Hedda commented Aug 9, 2024

For reference, here is a related feature request to the arduino-pico project:

More information in this discussion:

@maxgerhardt
Copy link
Owner

Let Arduino-Pico work on adding support for the chip first, then this platform will follow. It will definitely be added.

@Hedda
Copy link
Author

Hedda commented Aug 13, 2024

FYI, PontusO has a forked arduino-pico to a new arduino-pico-rp2350 repo where he got RP2340 working with an older version of the pico-sdk:

https://github.com/PontusO/arduino-pico-rp2350

An arduino-pico port is on it's way (https://github.com/PontusO/arduino-pico-rp2350). Unfortunatly there were a ton of PR's on the pico-sdk the past few days so it is not ready for prime time yet. It works fairly well in its current state though but this is using a 2 month old version of the pico-sdk.

Originally posted by PontusO in earlephilhower/arduino-pico#2226 (comment)

We do not know yet if he will leave that new arduino-pico-rp2350 repo as a a separate fork dedicated only to the RP2350 or if he or others will submit pull requests with changes from it to earlephilhower’s arduino-pico repo and use that as upstream for all picos, including both RP2040 and RP2350 in the same repository.

https://github.com/PontusO) in earlephilhower/arduino-pico#2226

@maxgerhardt
Copy link
Owner

It's slowly coming together.

Arduino-Pico working on RP2350. Debugging via debugprobe working with both ARM Cortex-M33 cores visible.

grafik

@maxgerhardt
Copy link
Owner

maxgerhardt commented Sep 3, 2024

Closing as #72 is merged into mainline now. We have updated RP2040 and RP2350 building + debugging support with the latest Arduino-Pico core as default.

Report issues with RP2350 separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants