|
From: | Alhad Palkar |
Subject: | Re: [lwip-users] lwip_write() blocks indefinitely |
Date: | Mon, 9 Nov 2015 14:05:13 -0800 |
Thanks Darius. Can you explain what you mean by output driver overrun? Does it mean my output driver is filling up LWIP buffers?I have an arm processor; using ThreadX as our RTOS and LWIP for our networks stack. I have written my own wifi driver based on the WICED wifi driver.Thanks,AlhadOn Sun, Nov 1, 2015 at 9:46 PM, Darius Babrauskas <address@hidden> wrote:Hi Alhad,Maybe one reason.Output driver overrun- packet are sending, but second packet overrun first.Try do test with delay:while(1) {
lwip_write();delay(10ms);
}Please, write about your system-hardware.DariusFrom: Alhad PalkarSent: Saturday, October 31, 2015 2:34 AMSubject: Re: [lwip-users] lwip_write() blocks indefinitelyAny reason why this would happen?On Fri, Oct 16, 2015 at 2:23 PM, alhadpalkar <address@hidden> wrote:
Hi,
I am using LWIP 1.4.1 and we are seeing a situation where lwip_write()
blocks indefinitely.
We are using a tcp socket, connecting to a remote socket. and then calling
lip_write over and over.
lwip_socket();
lwip_connect()
while(1) {
lwip_write();
}
The server is the netcat command running on a mac host.
In what situation would something like this happen?
Would this result because of improper configs in our lwipopts.h file?
Is there a cap on the size of the data buffer being passed to lwip_write?
Thanks,
Alhad
--
View this message in context: http://lwip.100.n7.nabble.com/lwip-write-blocks-indefinitely-tp25229.html
Sent from the lwip-users mailing list archive at Nabble.com.
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
[Prev in Thread] | Current Thread | [Next in Thread] |