Re: [lwip-users] blocked udp

alf of garibaldi pineda garcia <chano...@gmail.com> Sent: Wednesday, September 28, 2016 7:10 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] blocked udp Hi Noam, I was trying to avoid dealing with setting memory addresses for DMA transfers in Linux/RTOS, but running an OS might

Re: [lwip-users] blocked udp

s+noam=silrd@nongnu.org] *On > Behalf Of *garibaldi pineda garcia > *Sent:* Wednesday, September 28, 2016 3:34 PM > *To:* Mailing list for lwIP users > *Subject:* Re: [lwip-users] blocked udp > > > > Xilinx application notes seem to contradict the don't-mix > interrupt/poll

Re: [lwip-users] blocked udp

for lwIP users Subject: Re: [lwip-users] blocked udp Xilinx application notes seem to contradict the don't-mix interrupt/polling domains: Creating an lwIP Application Using the RAW API The lwIP RAW mode API is more complicated as it requires knowledge of lwIP internals. The typical structure

Re: [lwip-users] blocked udp

Oooh, I see. Then I believe I have to revisit my code because I based my design on their app note. Best, Gary On 28 September 2016 at 13:41, goldsimon wrote: > On the contrary: Xilinx does it perfectly right. They use their hardware > at interrupt level but feed rx packets

Re: [lwip-users] blocked udp

On the contrary: Xilinx does it perfectly right. They use their hardware at interrupt level but feed rx packets into lwip in the main loop. Simon Gesendet mit AquaMail für Android http://www.aqua-mail.com Am 28. September 2016 2:35:54 nachm. schrieb garibaldi pineda garcia

Re: [lwip-users] blocked udp

Xilinx application notes seem to contradict the don't-mix interrupt/polling domains: Creating an lwIP Application Using the RAW API The lwIP RAW mode API is more complicated as it requires knowledge of lwIP internals. The typical structure of a RAW mode program is as follows: 1. The first step

Re: [lwip-users] blocked udp

Dirk Ziegelmeier wrote: >> A second way to do it, not so preferred by some peoples but worked for me, >> is to add critical Sections [..]  > > Depends on what you mean by "critical section". If this is disable/enable > interrupts, that only works if you don't use an OS. Just to clarify this for

Re: [lwip-users] blocked udp

Hi, Dirk you're right, I'm using LWIP with the NO_SYS flag set to true. I'm somewhat confused, do I have two options? 1) Do a polling-like application that manages input/output without interrupts (I have no clue how to do this, should I follow the sample code?). 2) Send everything out when I

Re: [lwip-users] blocked udp

> > A second way to do it, not so preferred by some peoples but worked for me, > is to add critical > > Sections in code that call’s LwIP functions. Adding a critical section > means that you block other > > Tasks for a short time. Especially the TCP task from running. It means > that if you

Re: [lwip-users] blocked udp

To: Mailing list for lwIP users Subject: Re: [lwip-users] blocked udp Whenever your application wants to send, use tcpip_callback() macro to get a function called in tcpip thread and do the sending work there. Ciao Dirk -- Dirk Ziegelmeier * d...@ziegelmeier.net<mailto:d...@ziegelmeier.net> *

Re: [lwip-users] blocked udp

Is there another clean way to do it ? > > > BR, > Noam. > > > -Original Message- > From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On > Behalf Of Simon Goldschmidt > Sent: Wednesday, September 28, 2016 1:33 PM > To: lwip-users@nongnu.org &

Re: [lwip-users] blocked udp

. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Wednesday, September 28, 2016 1:33 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] blocked udp garibaldi pineda garcia wrote: > What I do is h

Re: [lwip-users] blocked udp

Simon :-) You answered In much less words then I did. Noam. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Wednesday, September 28, 2016 1:33 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] blocked

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

Re: [lwip-users] blocked udp

: Re: [lwip-users] blocked udp Hi Noam, I really appreciate your help and thank you for the time you've taken to reply. I believe my problem might be related to memory leaks, although I'm using a bare-metal application. The Zedboard has a dual Corex-A9 processor. So I process the video

Re: [lwip-users] blocked udp

priority. If your TCP priority is higher than the OS tick the OS > will not be able to musk the TCP stack > > Task when it enters its own critical sections. That also leads to > unpredictable system behavior and may cause > > hanging, lowness etc… > > > > > > Sorry fo

Re: [lwip-users] blocked udp

garcia Sent: Tuesday, September 27, 2016 12:31 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] blocked udp Hi Noam, I'm using the RAW API, I chose that for performance. By sending random data I mean I allocate a buffer in the ARM core and continuously send that through Ethernet/UDP. I'm

Re: [lwip-users] blocked udp

end > it from > > Within the LwIP context or via the route you try to send the video? > > > > BR, > > Noam. > > > > *From:* lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] *On > Behalf Of *garibaldi pineda garcia > *Sent:* Monday, Sep

Re: [lwip-users] blocked udp

] On Behalf Of garibaldi pineda garcia Sent: Monday, September 26, 2016 4:27 PM To: lwip-users@nongnu.org Subject: [lwip-users] blocked udp Hello all, I'm building a system which encodes video in a Zedboard FPGA and sends it out through the ethernet port. I have tested sending random data out

[lwip-users] blocked udp

Hello all, I'm building a system which encodes video in a Zedboard FPGA and sends it out through the ethernet port. I have tested sending random data out and it works, but when I try to use the data from the video source I manage to set the ARM core/network in a locked state. I've also tested the