Pi Pico Porting Steps

Hi,

I am currently looking for steps to start porting on new microcontrollers ( RP2040 and RP2350)

RP2350 seems promising to me since it has FPU, M33 processor, dual core,…etc.

I am going to start with RP2040 (M0+) since it has ChibiOS port and later I may look for the RP2350.

I see on Github the release of CSMIS for RP2040.

I don’t see in porting any info if the CMSIS or VSD are required or not. can someone confirm if they are required ?

I would like to go through baby steps to achieve my target…

2 Likes

niiice. I’m interested, especially in RP2350 !
any update @mr_byte31 ?

btw, it seems there’s PX4 for RP2040 Support for RP2350 · Issue #28266 · ArduPilot/ardupilot · GitHub
and this PCB looks interesting GitHub - vxj9800/openFC2040: This is an open-source flight controller board designed around RP2040 and PX4 . if gpt didn’t lie, I guess it should be out-of-the-box ok for RP2350.

I got stuck because there is no support of ChibiOS for RP2350 :frowning:
This is the price we have to pay to depend on RTOS with small community and few amount of contributors

@mr_byte31 do we actually need official support to be able to start? It seems there’s some first steps taken in Chibios already (did not test myself yet)

https://github.com/KarlK90/ChibiOS/pull/1/commits/248c135b579b4652173c3b02535afd080f69f488

https://forum.chibios.org/viewtopic.php?t=6372

Really? ChibiOS is a large and mature project.

The better question to ask is, “why has no major RTOS distro supported any release of the Pi Pico?”

I don’t have a specific answer for that, but I suspect the answer to that question may reveal some underlying issues with using the Pi Pico in the manner you desire.

That said, nothing stops you from being one of those contributors and porting yourself. That’s a big part of how any open source platform grows.

1 Like

When you say ‘large’ , you compare it to what?

Ok, so it’s not as “large” as say, the Linux kernel, but it has a core group of active developers, 15,000+ commits over 10 years, and enjoys active development across a well organized community between SourceForge/SVN and a GitHub mirror, which contains 87 community contributors in addition to the core team. That’s not a small undertaking by any measure.

But the bigger point in my post is the unanswered question. I think you should focus there rather than your criticism of open source RTOS in general.