Thanks for getting it working! I'd like to try out NuttX on the new Picos, so I'm excited development has started so quickly!
Not much advice for the other questions, but for number 2 maybe there could just be a raspberry-pi-pico2 board and the selection between ARM and RISCV is done via Kconfig? Either preprocessor statements or conditionally including the ARM/RISCV source files in Make.deps depending on the configuration settings? Matteo On Mon, Aug 26, 2024, 3:42 PM Marco Casaroli <marco.casar...@midokura.com.invalid> wrote: > Hello, > > I got my hands on some Raspberry Pi Pico 2 boards and I can finally run > NuttX on them. > > It took some work, since the M33 core is a bit different than the M0 on the > old RP2040. > > It is working now (nsh and usbnsh configs at least) and even ostest is > passing. > > For my initial PoC, I just edited many files in the rp2040 port but I will > create a new rp23xx port and I have some questions on how to organize the > files: > > 1 Where should I put the arch files? Should I put them in > arch/arm/src/rp23xx or should they be in a different path that could be > reused by the RISC-V and ARM boards? Should we make another arch subdir > like arch/multi? Or just have rp23xx in both risc-v and arm directories? If > so, then what about the files that are the same and could be reused. Where > to put them? Should I care to reuse these files or I can just copy them > over when we make the risc-v port? > > 2. How should I differentiate the boards? should I call > raspberry-pi-pico2-arm and raspberry-pi-pico2-riscv? > > 3. Some of the files could be shared / reused by rp2040 (ARM Cortex M0) and > rp23xx (riscv and ARM Cortex M33), how should I proceed to reuse these > files and have them in a common directory. What directory would be best? > > I plan on pushing a PR with the modifications later this week. > > Thank you! >
