Re: Integrating user code into a configuration

2024-04-29 Thread Alan C. Assis
I think you can do it, but keep in mind that the idea of board profile is
to test some specific feature or a set of features.

Probably you were expecting the raspberrypi-pico-w:audiopack to include the
WiFi since the board has WiFi support, but probably for the author of the
board profile his plan was just to focus on audio features.

It is normally easy to merge two board profiles, basically you start
configuring the original board profile (that one with WiFi support), then
you create a backup of the generated .config:

$ cp .config config_raspipico_wifi

Than you make distclean and configuregure that raspberrypi-pico-w:audiopack
and create a backup of the generated .config:

$ cp .config config_raspipico_audio

Thank you compare both configs moving the audio enabled symbols to wifi
config:

$ meld config_raspipico_wifi config_raspipico_audio

This is a good experience someone working with NuttX needs to master to
speed up the development process.

Best Regards,

Alan

On Sun, Apr 28, 2024 at 4:43 PM M. Edward (Ed) Borasky
 wrote:

> Thanks! That's a big part of what I'm trying to do. Should I open an issue
> on the raspberrypi-pico-w:audiopack not having a wireless configuration
> option? As it stands now I'd have to pull in the WiFi stack from the Pico
> SDK into a custom application like I'm planning to do with TinyUSB.
>
> --
> AlgoCompSynth by znmeb https://universodon.com/@AlgoCompSynth
>
> I don't have the hand muscles for strongly-typed languages.
>
> Sent with Proton Mail secure email.
>
> On Sunday, April 28th, 2024 at 4:11 AM, Alan C. Assis 
> wrote:
>
> > Hi Ed,
> >
> > Welcome to NuttX!
> >
> > We have a documentation explaining about it, please see section 3:
> >
> > https://nuttx.apache.org/docs/latest/guides/customapps.html
> >
> > Best Regards,
> >
> > Alan
> >
>
>


Re: Integrating user code into a configuration

2024-04-28 Thread M. Edward (Ed) Borasky
Thanks! That's a big part of what I'm trying to do. Should I open an issue on 
the raspberrypi-pico-w:audiopack not having a wireless configuration option? As 
it stands now I'd have to pull in the WiFi stack from the Pico SDK into a 
custom application like I'm planning to do with TinyUSB.

--
AlgoCompSynth by znmeb https://universodon.com/@AlgoCompSynth

I don't have the hand muscles for strongly-typed languages.

Sent with Proton Mail secure email.

On Sunday, April 28th, 2024 at 4:11 AM, Alan C. Assis  wrote:

> Hi Ed,
> 
> Welcome to NuttX!
> 
> We have a documentation explaining about it, please see section 3:
> 
> https://nuttx.apache.org/docs/latest/guides/customapps.html
> 
> Best Regards,
> 
> Alan
> 



Re: Integrating user code into a configuration

2024-04-28 Thread Alan C. Assis
Hi Ed,

Welcome to NuttX!

We have a documentation explaining about it, please see section 3:

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

Best Regards,

Alan

On Sun, Apr 28, 2024 at 1:36 AM M. Edward (Ed) Borasky
 wrote:

> I've just run across NuttX, and I think it's a good fit for my project.
> What I'm trying to do is develop computer music applications on
> microcontrollers. I'm mostly interested in the Raspberry Pi Pico W, but I
> also have some ESP32 S3, ESP 32 C3/C6, and Teensy 4.1 boards and would like
> the applications to run using the "sim" board on 64-bit Linux machines as
> well.
>
> My first target is the Pimoroni PicoVision. This has a Raspberry Pi Pico W
> as the main processor and a second highly overclocked RP2040 to drive the
> HDMI signal generation. It also has an I2S audio interface driving a DAC
> and stereo output jack. I won't be using the HDMI at the beginning. If I
> can get the PicoVision working, the same code should work on any Pico W I2S
> audio implementation.
>
> The existing raspberrypi-pico-w:audiopack does much of what I want except
> for a couple of minor issues:
>
> - The configuration doesn't seem to use the wireless on the Pico W. I'd
> like to be able to access the system via wireless, for example, to
> broadcast to a Bluetooth speaker.
> - I couldn't find a library in NuttX for MIDI or audio over USB. That
> isn't critical; those exist in TinyUSB.
>
> Which brings me to my main question: how do I use NuttX as a build system
> for my own code without integrating my code into a fork of NuttX
> repositories as I would for a formal contribution to the NuttX project?
>
> It's not a licensing issue; everything I do is open source for code and
> Creative Commons for documentation. It's mainly logistics; I don't want an
> end user to have to download NuttX and learn how to add a board or an
> application in order to use my code.
>
> Getting the PicoVision audio working with raspberrypi-pico-w:audiopack
> looks easy; I think all I have to do is make sure the I2S GPIO pin numbers
> are correct in the configuration. But is there documentation on how to use
> the media player? I couldn't find any. And how do I go about adding WiFi
> and Bluetooth to the configuration? I didn't see them in the existing Pico
> W one.
>
> I guess what I'm looking for is a guide for how to compose the pieces -
> board definitions, libraries and both NuttX and my own applications code -
> into a working configuration file that I can use.
>
> --
> AlgoCompSynth by znmeb https://universodon.com/@AlgoCompSynth
>
> I don't have the hand muscles for strongly-typed languages.
>
> Sent with [Proton Mail](https://proton.me/) secure email.


Integrating user code into a configuration

2024-04-27 Thread M. Edward (Ed) Borasky
I've just run across NuttX, and I think it's a good fit for my project. What 
I'm trying to do is develop computer music applications on microcontrollers. 
I'm mostly interested in the Raspberry Pi Pico W, but I also have some ESP32 
S3, ESP 32 C3/C6, and Teensy 4.1 boards and would like the applications to run 
using the "sim" board on 64-bit Linux machines as well.

My first target is the Pimoroni PicoVision. This has a Raspberry Pi Pico W as 
the main processor and a second highly overclocked RP2040 to drive the HDMI 
signal generation. It also has an I2S audio interface driving a DAC and stereo 
output jack. I won't be using the HDMI at the beginning. If I can get the 
PicoVision working, the same code should work on any Pico W I2S audio 
implementation.

The existing raspberrypi-pico-w:audiopack does much of what I want except for a 
couple of minor issues:

- The configuration doesn't seem to use the wireless on the Pico W. I'd like to 
be able to access the system via wireless, for example, to broadcast to a 
Bluetooth speaker.
- I couldn't find a library in NuttX for MIDI or audio over USB. That isn't 
critical; those exist in TinyUSB.

Which brings me to my main question: how do I use NuttX as a build system for 
my own code without integrating my code into a fork of NuttX repositories as I 
would for a formal contribution to the NuttX project?

It's not a licensing issue; everything I do is open source for code and 
Creative Commons for documentation. It's mainly logistics; I don't want an end 
user to have to download NuttX and learn how to add a board or an application 
in order to use my code.

Getting the PicoVision audio working with raspberrypi-pico-w:audiopack looks 
easy; I think all I have to do is make sure the I2S GPIO pin numbers are 
correct in the configuration. But is there documentation on how to use the 
media player? I couldn't find any. And how do I go about adding WiFi and 
Bluetooth to the configuration? I didn't see them in the existing Pico W one.

I guess what I'm looking for is a guide for how to compose the pieces - board 
definitions, libraries and both NuttX and my own applications code - into a 
working configuration file that I can use.

--
AlgoCompSynth by znmeb https://universodon.com/@AlgoCompSynth

I don't have the hand muscles for strongly-typed languages.

Sent with [Proton Mail](https://proton.me/) secure email.