Hi Matteo,

I don't know if the guide you are reading is this same:

https://cwiki.apache.org/confluence/display/NUTTX/Porting+Guide

There is a lot of documentation that we need to move to our official page.

After creating the arch hardware header files I think you can start the
start C file with the initialization process.

I miss a diary (or step by step guide) on how to port NuttX to a new
architecture, explaining exactly the questions you are having.

The ports I've made so far have been for chips with architectures that were
already supported.

Maybe a suggestion that I can give you is looking at the git history to
understand how other people ported NuttX to a new architecture.

Maybe the LM32 port from Ramtin Amin could help you, look his initial
patches:

$ gitk arch/misoc/src/lm32/

Unfortunately, almost all new ports start with the contributor squashing
all the commits (see FE310 for reference, at least the comments still there
in the initial commit) or just drop dozens of files.

So, if you can, please start writing your diary with the steps you are
taking and why. It could become an official guide.

BR,

Alan

On Wed, Jul 24, 2024 at 10:15 PM Matteo Golin <matteo.go...@gmail.com>
wrote:

> Hello all,
>
> I am working on a port for NuttX to the Raspberry Pi 4 Model B, for which I
> am using Gregory's previous port to the BCM2708 as a reference.
>
> I've read through the documentation available here
> <https://nuttx.apache.org/docs/latest/> to get a better grasp of how NuttX
> works "under the hood", but I'd still like to know more. The port started
> out rosy with copying register addresses and bitmasks from the datasheet to
> header files, and now that I've completed that, I'm not sure of where to
> start. There seem to be a number of interfaces that need implementing in
> order to make a pretty minimal boot of NuttX, but I'm not sure where (if
> anywhere) I can determine a list of what needs to be implemented or if
> there's a general process to it.
>
> So far my best idea is to re-review the documentation to see if I can get
> more to stick, and in the meanwhile also try to read through and understand
> an existing port's implementation for one of the simpler MCUs.
>
> If there are any suggestions as to what steps I should take to facilitate
> porting NuttX or understanding more about the OS, I would be eager to hear
> them!
>
> Thanks,
> Matteo
>

Reply via email to