Re: [lwip-users] best approach to lwip using FreeRTOS

[Francois Bouchard]

Hi Sergio,

> I suppose all examples of lwip in FreeRTOS site uses the NO_SYS=0, right ?
Yes.

> So I guess I have to create a task to mimic the timer interrupts [...]
No, the tcp/ip core thread will do that for you.

>(the luminary´s previous implementation just flags to the main loop from
the ISR, and handle everything in this loop).
Now, with NO_SYS=1 your Ethernet Rx ISR can Give a binary semaphore onto
which the Ethernet task is pending on.

Is there a lwip port for your specific plateform on FreeRTOS.org?

Francois


----- Original Message -----
From: "Sergio Sider" <address@hidden>
To: "Mailing list for lwIP users" <address@hidden>
Sent: Friday, March 13, 2009 11:20 AM
Subject: Re: [lwip-users] best approach to lwip using FreeRTOS


> Hi François,
>
> I suppose all examples of lwip in FreeRTOS site uses the NO_SYS=0, right ?
> Actually I am using Luminary´s LWIP implementation (NO_SYS=1) , having
> to deal with lwip timeout counters. So I guess I have to create a task
> to mimic the timer interrupts and another task to handle the actual
> ethernet interrupts (the luminary´s previous implementation just flags
> to the main loop from the ISR, and handle everything in this loop).
> Sorry for my ignorance, but I am still a little confuse if I can use
> the raw api with NO_SYS=0...
>
> thanks for your message,
> Sergio.
>
> On Fri, Mar 13, 2009 at 11:59 AM, Francois Bouchard
> <address@hidden> wrote:
> > Hi,
> >
> > If you are used to the raw API, I suggest to continue with it. The raw
API
> > takes a bit less RAM, and its a bit faster than the other two APIs. As
an
> > example, with the raw API and a OS (FreeRTOS in your case, and mine
too!)
> > you can implement an echo server with only 2 tasks:
> >
> > 1) an Ethernet task that receive/manage Rxed frames
> > 2) and the core TCP/IP thread
> >
> > Francois
> >
> >
> > ----- Original Message -----
> > From: "Sergio Sider" <address@hidden>
> > To: "Mailing list for lwIP users" <address@hidden>
> > Sent: Friday, March 13, 2009 7:01 AM
> > Subject: [lwip-users] best approach to lwip using FreeRTOS
> >
> >
> >> Hi guys,
> >>
> >> I posted this message on the FreeRTOS list and they suggested me to
> >> post it here...
> >> here it goes:
> >>
> >> Hi all,
> >>
> >> I need an opinion:
> >>
> >> I am used to lwip raw interface, and like it´s simplicity and callback
> >> approach.
> >>
> >> For years, I was using in my embedded programs, a simple cooperative
> >> "multitasking" interface, where I call all tasks sequentially in the
> >> main loop, using a simple ticker.
> >>
> >> I am now starting to try FreeRTOS...
> >>
> >> What´s the best way to use lwip ?
> >> Continue to use raw api (I suppose I have to do it inside one single
> >> task)? or start using netcon to take advantage of the multitasking?
> >>
> >> I know the answer might depend on the complexity of my design, but is
> >> one approach way better than the other so I just should not think
> >> about it ?
> >>
> >> Thanks for any advice!
> >> Sergio P. Sider
> >>
> >>
> >> _______________________________________________
> >> lwip-users mailing list
> >> address@hidden
> >> http://lists.nongnu.org/mailman/listinfo/lwip-users
> >>
> >
> >
> >
> > _______________________________________________
> > lwip-users mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/lwip-users
> >
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>