nuttx icon indicating copy to clipboard operation
nuttx copied to clipboard

Raspberry pi 4 model B support

Open TaiJuWu opened this issue 1 year ago • 8 comments

Can Nuttx support raspberry 4 model B? Or anyone work on this board?

TaiJuWu avatar Jan 22 '24 23:01 TaiJuWu

@TaiJuWu the initial support to Raspberry Pi board (the first board) was removed by Greg some years ago because nobody was interested to still working in the port: https://bitbucket.org/patacongo/obsoleted/src/master/Patches/Remove-arch-bcm2708-2019-01-02.patch

If you want to work on it, you can look that initial support and use it as reference.

alandeassis avatar Jan 23 '24 21:01 alandeassis

@TaiJuWu the initial support to Raspberry Pi board (the first board) was removed by Greg some years ago because nobody was interested to still working in the port: https://bitbucket.org/patacongo/obsoleted/src/master/Patches/Remove-arch-bcm2708-2019-01-02.patch

If you want to work on it, you can look that initial support and use it as reference.

Thanks for your information.

TaiJuWu avatar Jan 23 '24 23:01 TaiJuWu

Checking if this is in development at all? I am interested in contributing to get support for this board.

linguini1 avatar Jun 28 '24 20:06 linguini1

Checking if this is in development at all? I am interested in contributing to get support for this board.

No, I am not working on it. Welcome to take it over, thanks.

TaiJuWu avatar Jun 29 '24 21:06 TaiJuWu

Could this issue be assigned to me? I have begun work on it.

linguini1 avatar Jul 23 '24 00:07 linguini1

Could this issue be assigned to me? I have begun work on it.

Done, thanks.

xiaoxiang781216 avatar Jul 23 '24 02:07 xiaoxiang781216

So I have an initial implementation for this board (the 4GB variant is all I have access to for testing right now) which boots successfully and has NSH running with a UART console. It passes the ostest as well.

Obviously I plan to implement some drivers for the board so it can actually be used for programming/development (I2C, remaining UARTs, GPIO, etc.). I am wondering, however, at what point is a port to a new board considered "good enough" to be merged? I imagine that full support for everything on the board (like HDMI ports, Bluetooth, etc.) does not have to be implemented to be merged, but is there a guideline on how complete it must be at a minimum to become part of the main source tree?

I ask only because I think that at some point in the development process I'd like to be able to call it "complete enough" to allow for it to be merged and more accessible to others to make changes/add features.

linguini1 avatar Aug 07 '24 01:08 linguini1

it's enough to implement uart and timer driver to ensure the port enter nsh correctly.

xiaoxiang781216 avatar Aug 07 '24 05:08 xiaoxiang781216