Can't build sample "telnet" for raspi_pico_w.

RE: Can't build sample "telnet" for raspi_pico_w.

Raoul — Tue, 21 Nov 2023 14:25:48 GMT

My pleasure!

Best regards,

Raoul

RE: Can't build sample "telnet" for raspi_pico_w.

Jerry Easley — Tue, 21 Nov 2023 13:35:33 GMT

Hi Raoul,

Thank you so much; your replies are very helpful!

Best Regards,

Jerry

RE: Can't build sample "telnet" for raspi_pico_w.

Raoul — Tue, 21 Nov 2023 12:40:03 GMT

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.

RE: Can't build sample "telnet" for raspi_pico_w.

Jerry Easley — Tue, 21 Nov 2023 07:46:08 GMT

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

RE: Can't build sample "telnet" for raspi_pico_w.

Raoul — Mon, 20 Nov 2023 21:51:16 GMT

Hi Jerry!

[quote user=""]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.[/quote]

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