josephjah wrote:
> [..] I've taken a look [at LWIP_TCPIP_CORE_LOCKING] and it appears that this
> is
> designed to be used with NO_SYS==0
That's correct. When using NO_SYS==1, you're back on your own with the
statement that the lwIP
core is not meant for concurrent access. :-)
Simon
Thanks for the advice, Dirk. I've taken a look and it appears that this is
designed to be used with NO_SYS==0, currently for my application I have
NO_SYS==1. It appears that I need to do some significant re-engineering of
the core's locking mechanism to make this work for my context, but I suspect
Try to use lwIP 2.0.0 core locking feature instead, it does what you try to
do with your own mutexes:
http://www.nongnu.org/lwip/2_0_0/group__lwip__opts__lock.html#ga8e46232794349c209e8ed4e9e7e4f011
http://www.nongnu.org/lwip/2_0_0/pitfalls.html
Ciao
Dirk
--
Dirk Ziegelmeier *
