Is Nordic planning to make full specification TCP/IP middleware?

RE: Is Nordic planning to make full specification TCP/IP middleware?

NordicIsMyLife — Wed, 20 Jan 2016 00:35:43 GMT

How wonderful!

RE: Is Nordic planning to make full specification TCP/IP middleware?

Petter Myhre — Tue, 19 Jan 2016 17:26:18 GMT

We have ported the lwIP stack to nRF5 to showcase the ability of the nRF5 to run third-party stacks.

The lwIP is configurable, and the stack available in the SDK is only one configuration, a configuration we found suitable for the flash and RAM we have available on our device. See the header files external/lwip/src/port/arch/lwipopts.h and external/lwip/src/port/arch/cc.h for details of our lwIP configuration.

See this for detailed information about lwIP.

For more information about the different configurations please have a look at this, specifically Configuring lwIP in the right column.

I also found this, talking about the limitations of lwIP. I'm not an expert on lwIP, but I hope this is of help. If you have any specific requirements or questions it might be easier to give you a more precise answer.

RE: Is Nordic planning to make full specification TCP/IP middleware?

NordicIsMyLife — Tue, 19 Jan 2016 12:43:35 GMT

I think that LWIP is different from full scale TCP/IP because LWIP has small resource. Would you please tell me what is the difference between LWIP and full scale TCP/IP?

RE: Is Nordic planning to make full specification TCP/IP middleware?

Petter Myhre — Tue, 19 Jan 2016 09:29:31 GMT

Could you explain a bit more about what you need?