On Thu, Dec 19, 2024 at 9:02 AM Aaron M <aaron.lists...@minn-tek.com> wrote:
> Sorry if this is inappropriate for the list, but I'm a relative noob to
> Nuttx, and I'm just trying to find my way.  I'll go elsewhere if you
> point me in the correct direction for questions like this.

Welcome to the NuttX community Aaron! :-)


> My exposure to Nuttx has been strictly limited to Sony's Spresense, and
> I have a suitable working environment in VSCode with Sony's SDK.  But if
> I want to build for, say, the FRDM KL-25, or the RPi Pico 2, can I use
> the same environment, er, somehow?  Do I need to download separate
> copies of the repo of Nuttx for each board?

Long story short, you can use the same repo clone for totally
different builds, just remember to `make clean distclean` before a new
build. Each new build is initiated with `./tools/configure.sh
[switches] <board:config>`.

For sure you can have multiple repo clones aka workspaces to work on a
different projects in parallel :-)

See documentation :-)

https://nuttx.apache.org/docs/latest/quickstart/index.html


> This link has a nice overview, but it doesn't cover how to handle
> multiple boards:
> https://www.cocoacrumbs.com/blog/2021-10-25-nuttx-on-the-stm32f769-disco-board/

There is another way to deal with the task and many of us use this
approach called "out of tree boards" - you keep one clone of nuttx and
nuttx-apps in one place, and keep your projects in a separate place.

https://nuttx.apache.org/docs/latest/guides/customboards.html


> Thanks for any insight, and my deepest apologies if this is the wrong
> place for these questions.

You are always welcome to ask questions. We often discuss different
tasks and ideas here openly so everyone can learn new stuff and get
better insight / understanding this is our ultimate goal :-)

If you miss something in the documentation you are more than welcome
to send PR with the missing contents.. documentation is part of the
nuttx.git repo :-)

Have fun! :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Reply via email to