[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] blocked udp

From: Dirk Ziegelmeier
Subject: Re: [lwip-users] blocked udp
Date: Wed, 28 Sep 2016 12:59:01 +0200

Whenever your application wants to send, use tcpip_callback() macro to get a function called in tcpip thread and do the sending work there.


Dirk Ziegelmeier * address@hidden * http://www.ziegelmeier.net

On Wed, Sep 28, 2016 at 12:52 PM, Noam Weissman <address@hidden> wrote:
Hi Simon,

What is the preferred way to send data from within LwIP context.

Beside running sys_timeout and hooking a function to it ?

If I want to send data at a high rate and I will set sys_timeout to say 1ms it will cause load
on the system. Is there another clean way to do it ?


-----Original Message-----
From: lwip-users [mailto:lwip-users-bounces+noam=address@hidden] On Behalf Of Simon Goldschmidt
Sent: Wednesday, September 28, 2016 1:33 PM
To: address@hidden
Subject: Re: [lwip-users] blocked udp

garibaldi pineda garcia wrote:
> What I do is have an interrupt to receive the data from the FPGA and,
>in the main program loop (would this be the LWIP context?),

I guess so. That would mean you don't use an OS but use lwIP in NO_SYS=1 mode.

> I call a function to send data out. I also have an interrupt for the
> receive function for the LWIP data.

That would mean you call the lwIP TX functions from main loop while calling the RX functions from ETH RX interrupt. That's not supported and this most probably is your problem.


lwip-users mailing list
lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]