tcpip_init changes for lwip 2.02

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

tcpip_init changes for lwip 2.02

GuyH
Hi,

I had my application running with freertos OS with lwip 1.4 and I just moved
to SDK 18.1 with lwip 2.02 - I've noticed that one of the changes for the
2.02 version is omitting the call to lwip_init from inside tcpip_init (it is
now remarked in #if 0).
Why was this omitted? And should I add then lwip_init myself before? Since
the memory for instance is not initialized now and there is an assert when
taking a semaphore afterwards.

Thanks,
Guy.




--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: tcpip_init changes for lwip 2.02

goldsimon@gmx.de


Am 2. August 2018 15:47:21 MESZ schrieb GuyH <[hidden email]>:
>Hi,
>
>I had my application running with freertos OS with lwip 1.4 and I just
>moved
>to SDK 18.1 with lwip 2.02

What is SDK 18.1? I guess you are talking about some vendor-modified version of our stack...

> - I've noticed that one of the changes for
>the
>2.02 version is omitting the call to lwip_init from inside tcpip_init
>(it is
>now remarked in #if 0).

Ok, this is definitively not our code you're looking at there. Can't really help you there I guess. You can compare the sources at hand 28th our official 2.0.2 sources of that helps...

Simon

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users