Marcel M. wrote:
Both options can be possible. You can dedicate each connection a task,
or use one task for all.
Then i prefer a own task for each connection(port).
I see that FreeRTOS STR912 port
uses uIP(not lwIP). This may cause some problems
because you have to provide your sys_arch implementation in this case.
Which lwIP files must be ported for the STR912 system? For the STR912 i have
got a complete ethernet library from ST.
Library? What kind of a library? I don't think it's a complete stack.
I used only lwIP raw and netconn_api layers.
Isn't the socket-API easier to use? Just listen, bind and accept in each
Task!? Or must i use semaphores too? Are there any restrictions if i use
lwIP-socket functions?
As far as I know, sockets arch do not fit completetly into lwIP
model.(Please forgive me if I misunderstood the stuck arch)
On the other hand, it is supported. So you can choose your own way.
I'm succesfully binding 2 ports and using connections at the same time,I
think you can do more easily.
You used semaphores to make lwIP threadsafe? Right?
FreeRTOS uses queue mechanism at this point(implementing mailboxes for
lwIP). Moreover, semaphore is nothing but a unity size queue for
FreeRTOS. FreeRTOS supplies sys_arch functions for threading support.(I
think this is the recommended way in lwIP) If you go for ST you have to
implement your own sys_arch functions. You can safely use different
threads in FreeRTOS for lwIP without any problem,that's for sure. The
threading
problem you mentioned in your first post is pointing to something
different, I guess. It is related to lwIP porting, rather than lwIP
itself. Since FreeRTOS
is providing a thread safe implementation, you won't lack threading
support either,as long as you stick to the implementation.
Regards
Marcel
Kind Regards,
Caglar AKYUZ
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
