Can't build sample "telnet" for raspi_pico_w.

[Jerry Easley]

This may be a policy query rather that a technical issue.

Under VSCODE/nRFCONNECT extensions, I created a new project from samples, namely 'telnet'.

I created a build configuration for the nrf52840dk successfully; I even built it and flashed it to the nrf52840dk; it didn't work of course because there is no wlan or eth0 on that board.

I attempted to create a build configuration for the raspi_pico_w board; the build configuration failed with all kinds of error messages.

In addition i built this project under the Zephyr toolchain and for the rasp_pico_w without incident.

I would like to use the VSCODE/nRFCONNECT extensions environment to build projects for non Nordic boards like the raspberry pi variants as well as TI  and STM  boards.

So, my question is, am I facing a technical issue here, that possibly I can fix, or am I up against a sort policy issue concerning non Nordic products.

This is more of convenience issue for me because I can build for the non Nordic boards under the Zephyr toolchain/SDK.

Best Regards,

Jerry

[Raoul]

Hi Jerry!

So, my question is, am I facing a technical issue here, that possibly I can fix, or am I up against a sort policy issue concerning non Nordic products.

If I understood your question correctly, the answer here is that it's a technical issue. As far as I know, there is nothing in the VS Code extension that's deliberately blocking your build from working since it's "not Nordic".

In fact I think that the VS Code extension just calls "west build" under the hood, so it might be an nRF Connect SDK technical issue rather than an extension technical issue.

Note that nRF Connect SDK is not exactly a "superset" of Zephyr. It also makes a few modifications, I believe.

More importantly, you should be careful because I think there's actually a license preventing you from using the nRF Connect SDK with other boards. So please tread carefully here. For your Pico, TI and STM boards you'll probably have to stick to vanilla Zephyr.

I hope that answers your questions. If you still want me to clarify anything with the VS Code extension developers, let me know.

Best regards,

Raoul

[Jerry Easley]

Hi Raoul,

Thank you so much for your timely reply.

If it is not too much trouble, could you check on that licensing restriction?  If yes, just forget it and close the ticket.

Best Regards,

Jerry

[Raoul]

Hi again,

I found a blog post from 2017, on what were then our new license scheme:

 Introducing Nordic’s new software licensing schemes 

I think these are virtually identical to this day. For example, see the current license on our sdk-nrf repo:

https://github.com/nrfconnect/sdk-nrf/blob/main/LICENSE

In reality, NCS consists of components with varying licenses, including some permissive ones I believe. But those are likely just the components that are inherited from Zephyr, so I recommend you to just use vanilla Zephyr instead.

You should also be aware of West SPDX, a tool that helps helps summarize the licenses in your codebase. But I don't have experience with using it.

See also:

 nRF Connect SDK licenses 

 How can i disable as many 5 clause licensed parts of the nrf connect sdk except as absolutely necessary to use the hardware. 

I hope that helps!

Best regards,

Raoul

[Jerry Easley]

Hi Raoul,

Thank you so much; your replies are very helpful!

Best Regards,

Jerry

[Raoul]

My pleasure!

Best regards,

Raoul