[lwip-users] RE: [lwip] lwIP in a non-OS environment

[DASILVA VINCENTE BIT]

I am using uCOS as the HAL. This means that lwip will run on any processor
that uCOS has been ported to. This is literally any processor on the
market... see http://www.ucos-ii.com/

Vicente

-----Original Message-----
From: Paul Sheer [mailto:address@hidden
Sent: 13 February 2002 09:29 AM
To: address@hidden; Carsten Thomas; Adam Dunkels; address@hidden
Subject: Re: [lwip] lwIP in a non-OS environment



I have the EXACT answer to your question

I am developing an OS, called PaulOS that filfulls all
of your requirements.

        - it operates in a single thread
        - it employs NO locking whatsoever
        - it has a minimal POSIX layer for convenience
        - it runs on the ARM7TDMI
        - it is written entirely in C with only 2 or 3
                architecture specific files
        - it currently runs lwIP during the idle
                cycles of any POSIX call where the POSIX
                call blocks waiting for an event or
                timeout.
        - it does not use interrupts except where
                absolutely necessary

On the ARM, the entire image is 90kB, which includes
a minimal termios layer, web server and ARM serial
driver.

Do you want to create a port for your processor?

best

-paul



On 2002.02.12 11:54 Alexander Groß wrote:
> Hello everybody,
> 
> I have some questions concering the usage of the lwIP-stack in an
> environment where no operating system could be used. We would like to
> integrate TCP/IP support to our PLC solutions, so the whole applications
is
> very time-critical.
> I didn't find much about lwIP w/o OS on raw API in the documentation I
hope
> you can help me to reach a decision if I could use lwIP.
> 
> For developement purposes I'll use the Keil MCB-167NET Board. It is
equipped
> with an Infineon 167 and the Crystal CS8900 ethernet controller. We can't
> support an OS since we just want to build a network layer that can be used
> with any of our existing applications (which are not only PLCs). The
network
> layer has to be called cyclic from the application to make sure that CPU
> time is shared between application and network layer. It is also
> unacceptable for us to wait for some kind of processing (i.e. semaphores)
> since we have time-critical applications with a maximum time per cyle
(i.e.
> PLC).
> 
> I would have to implement a state machine to hande the network layer,
which
> is no problem.
> 
> There are some missing information:
> - Does lwIP support an environment decribed above (no OS, no wait timers)?
> - If I use the raw API, is there some "intelligence", like TCP fast
> retransmit/recovery, implemented or will I have to set up my own
algorithms?
> - How can I give lwIP CPU cycles that it can process enqueued packets?
> 
> I hope you can clear my view!
> Thanks in advance.
> 
> Regards,
> 
> Alex
> 
> _________________________________________
> 
> Alexander Groß
> Student in Computer Sciences
> 
> SYS TEC electronic GmbH
> August-Bebel-Straße 29
> 07973 Greiz
> Germany
> 
> Phone: +49 36 61 / 62 79 - 0
> Fax: +49 36 61 / 62 79 - 48
> www: http://www.systec-electronic.de
> e-mail: address@hidden
> _________________________________________
> 
> [This message was sent through the lwip discussion list.]
> 
Paul Sheer Consulting IT Services . . . Tel . . . +27 21 761 7224
Email . . . address@hidden . . . . . . Pager . . . 088 0057245
Linux development, cryptography, recruitment,  support,  training
http://www.icon.co.za/~psheer . . . . http://rute.sourceforge.net
L I N U X . . . . . . . . . . . .  The Choice of a GNU Generation
[This message was sent through the lwip discussion list.]
[This message was sent through the lwip discussion list.]