Hello lwip,
I am using lwIP 2.0 and I discovered LWIP_TCPIP_CORE_LOCKING option (I know it
was there also before).
In my project with OS (and many threads), I have one OS thread say "App" in
which I create "tcpip thread" and then in "App" thread I am using SOCKETS API.
Interrupt manages MAC
It depends on what you actually do when you "use" the sockets.
If you trust your port and driver, then debug your app and do a traffic
capture. Is it possible your app is starving the lwIP task as Noam
suggests ? Where do your messages get lost ? Are they in the wire ? Do
they enter the lwIP
Hi,
Is this code actually a task ?
If it is please add a small delay at end of loop.
Adding a vTaskDelay call at end of loop is common practice. This is important
In order not to starve other tasks running in your system.
I do not know/think that adding the delay will solve your problem but
I don´t now what running apps you mean which are close to that problem.
When I use the socket api everything works, so can it be a driver or port
problem?
--
View this message in context:
http://lwip.100.n7.nabble.com/Recv-UDP-Problem-tp27826p27828.html
Sent from the lwip-users mailing list
You should probably get some ideas if you run a sniffer, as I would
probably too if I see your capture file.
As a first guess, I bet you are losing frames in your driver. You should
first run an application you know it works (like the ones in "apps" or
in the "contrib" tree) before diving into
Hi,
I am able to receive UDP messages but it only works sometimes. In my example
I sent a UDP message and I get an automatic reply. But this only works every
3-6 messages. What can be the problem. I am working on a Atsame70 with RTOS
and Lwip 1.4
do {
if (ERR_OK ==
