Thanks for you answer !
Yes you're probably right.
Currently I remove the interrupt ISR because it's not as useful as I thought
.
Maybe I'll use it in order to improve the reactivity to received frames in
an RTOS context .
Moreover , after a deep read of the MAC part off the lpc , It seems easy t
Thank you, Kieran! This solved the problem! :-)
Marco
Kieran Mansley schrieb:
Upgrading to 1.3.1 will help. Here is the CVS commit that fixed this
problem:
http://cvs.savannah.gnu.org/viewvc/lwip/src/include/lwip/err.h?root=lwip&r1=1.13&r2=1.14
Kieran
_
Hi,
if you are insterested in, here is a rewritten contrib socket sntp
client example to use netconn api.
I have test it against WinXP with lwip 1.3.1 on LM3S9b92. You have to
define SNTP_SERVER_ADDRESS variable and LWIP_SO_RCVTIMEO to enable
UDP timeout.
A piece of customization(e.g. remove ca
Hi Yann,
> In the first case the RX buffer descriptors of the MAC controller is done
> totally in the ISr. In the second case, I can only update descriptors to
> release the MAC buffer in my_netif->input. But then there could be
> concurrency access from ISR and main thread :-/ Is it possible to a
On Thu, 2009-10-08 at 15:28 +0200, Marco Jakobs wrote:
> Hi Kieran,
>
> i'm using 1.3.0 with Free RTOS on an AT91SAM7X512.
>
> My "basic idea" for the final solution is that LWIP should have
> incoming data in its buffers. With this, if i call
>
> tgtxcon->recv_timeout=1;// Timeout setzen
Hi Kieran,
i'm using 1.3.0 with Free RTOS on an AT91SAM7X512.
My "basic idea" for the final solution is that LWIP should have
incoming data in its buffers. With this, if i call
tgtxcon->recv_timeout=1; // Timeout setzen
txbuf=netconn_recv(tgtxcon); //Daten empfangen
every 20ms, it
What version of lwIP are you using? I have a vague recollection of a
bug in an earlier version that resulted in a timeout error being treated
as fatal.
Kieran
___
lwip-users mailing list
lwip-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/
Hi to all,
for the last hours i try to solve a problem with a TCP write and receive.
First, the implementation of the receive function netconn_recv is not as
lucky as this will not return by default.
But with information on this list, i reconfigured the netconn_recv to use
the timeout:
tgtxco
Hello, because the problem is difficult to evaluate, the customer say me
different option.
a) Only two socket ( one for TX an RX) and the other for TX asycronous
messages.
It´s can be Ok, because i can create two task to do this and not use select
only the function recv and in the other task(with
On Wed, 2009-10-07 at 15:54 -0400, David Shmelzer wrote:
> I traced the problem to conn->err being assigned a value in separate
> threads.
> One in recv_tcp() and another in netconn_recv().
>
> recv_tcp() is called from the tcpip_thread and netconn_recv() is called
> from a separate thread.
> Am
10 matches
Mail list logo
