[Top][All Lists]

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

Re: [lwip-users] UDP Sender omapl137

From: Jaime Fernandez Hoffiz
Subject: Re: [lwip-users] UDP Sender omapl137
Date: Sun, 6 Mar 2016 13:31:54 -0600

Thank you Simon for the prompt response.

I have not reason for calling lwip_init() instead of tcpip_init(). I'm just trying to understand what pieces are required to simply send a UDP packet. After looking at a few other examples, and the FreeRTOS example for the AVR32, what I'm trying to do makes sense if I were to run bare metal. Which is what I see in a bunch of other examples like the omapl138 (Sitara). 

Your respond confirms what I've seen in other OS examples (not bare metal) of the lwip port and I will cease from going down that path. So even for a udp sender sounds like I still need to call the tcpip_thread.


On Sun, Mar 6, 2016 at 1:09 PM, address@hidden <address@hidden> wrote:
Jaime Fernandez Hoffiz wrote:
What I'm trying to do now, is to understand a little better to layers of lwip and create a simple udp sender without having to call: [..]

Why do you want to call lwip_init() instead of tcpip_init()?
It can work, but you need to adapt the rest of your port to use NO_SYS==1, too: in your configuration, input packets probably are put on tcpip_thread's input queue and since the thread is not started, noone handles them.


lwip-users mailing list

reply via email to

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