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 <zn...@proton.me.invalid> 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 <acas...@gmail.com> > 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 > > > >
