Hi Bill,

There is not a usbsmp or smpusb board profile as Greg said, but you can
create one this way:

First configure the usbnsh board profile:
$ ./tools/configure.sh raspberrypi-pico:usbnsh

Compile: (you will need to export to PICO SDK, it is documented in our site
https://nuttx.apache.org/docs/latest/index.html )
$ make -j
Copy the generated nuttx.uf2 to your board and config that NSH is working
over USB.

If everything is working, you can continue:

Copy the created .config to config_raspico_usbnsh
$ cp .config config_raspico_usbnsh

Clear the configuration:
$ make distclean

Configure the existing smp board profile:

./tools/configure.sh raspberrypi-pico:smp

You don't need to compile, just copy this new .config to config_raspico_smp
$ cp .config config_raspico_smp

Now you can use a text diff config tool like meld or kdiff3 to compare
these two config files and move things related to smp to the usbnsh:

Note: Since you are going to modify the config_raspico_usbnsh you can save
a copy of this file, just in case you mess something in the first try.

$ meld config_raspico_smp  config_raspico_usbnsh

Basically move things related to SMP from the left (config_raspico_smp)
side to the right side (config_raspico_usbnsh).

Save the modifications to config_raspico_usbnsh and now copy it to .config:

$ cp config_raspico_usbnsh .config

$ make -j

Now you will have a nuttx.uf2 that will have both features.

I can create it for you in a few minutes, but I think this is the kind of
practice that will improve your NuttX skills.

BR,

Alan

On Fri, Aug 9, 2024 at 5:38 PM William Martin <w...@wwmartin.net> wrote:

> Greetings,
>
> No luck getting an index of articles from the mailing list bot, so my
> request is: can some kind soul tell me where to find out how to use the
> smp built-in for NuttX, and how do I make an option, such as 'smpusb'
> for the configure.sh tool to create an smp version with usb terminal
> instead of serial port.
>
> Thanks very much,
>
> Bill Martin
>
> ps: I'm not a Linux wizard, rather a retired hardware engineer...
>

Reply via email to