[RTEMS Project] #1712: Add LWIP Support to RTEMS

[RTEMS trac]

#1712: Add LWIP Support to RTEMS
----------------------------+----------------------------
 Reporter:  Joel Sherrill   |       Owner:  Joel Sherrill
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:  6.1
Component:  network/legacy  |     Version:  4.11
 Severity:  minor           |  Resolution:  fixed
 Keywords:                  |  Blocked By:
 Blocking:                  |
----------------------------+----------------------------
Changes (by Joel Sherrill):

 * status:  reopened => closed
 * resolution:   => fixed


Old description:

> This port was done by Marcello Presulli <m.presulli at embed-it.com> and has
> been in my inbox for a while.  I think I have merged most of their BSP
> specific work but the lwip has been pending.  They managed to run
> LWIP+SNMP and an application in something like 128K RAM
>
> Here are some email fragments about it.
>

>
> For now we have just finished to port the latest lwip-1.3.2 based on the
> latest rtems 4.9.4 version successfully including
> a test_app for pings.
>
> We have stressed the stack with ping floods (packetsize 1400 Bytes
> interval ~150ms) about 250.000 sequences or more without
> packet losses and an average latency of 2ms.
>
> Additional we have adopted a new bsp target for the mcf5225x platform.
>

> To lwip now:
>
> we integrated it directly via the autoconfigure/automake process under
> the
> rtems cpukit/liblwip subtree and therefore it gets built with rtems
> when u configure it with --enable-networking=lwip appropriately.
> The driver on the other side we put it in libcpu/m68k/mcf5225x and it got
> built in the library context of the librtemsbsp.a.
> The driver has only 2 references on lwip headers ...
>
> To the bsp:
>
> The bsp we have adopted from mcf52223 and have created it as a own
> bsp-target=mcf5225x also via the autoconfig/automake mechanism.
> In the bsp itself i have modified the bsp_get_CPU_clock_speed() and some
> improvements in the console driver and PIT2 timer interrupt.
> The bsp_start() we have defined as weak symbol so we don't have to touch
> the "empty" bsp_start() of rtems coz it's platform-circuit
> specific you know.

New description:

 This port was done by Marcello Presulli <m.presulli at embed-it.com> and has
 been in my inbox for a while.  I think I have merged most of their BSP
 specific work but the lwip has been pending.  They managed to run
 LWIP+SNMP and an application in something like 128K RAM

 Here are some email fragments about it.



 For now we have just finished to port the latest lwip-1.3.2 based on the
 latest rtems 4.9.4 version successfully including
 a test_app for pings.

 We have stressed the stack with ping floods (packetsize 1400 Bytes
 interval ~150ms) about 250.000 sequences or more without
 packet losses and an average latency of 2ms.

 Additional we have adopted a new bsp target for the mcf5225x platform.


 To lwip now:

 we integrated it directly via the autoconfigure/automake process under the
 rtems cpukit/liblwip subtree and therefore it gets built with rtems
 when u configure it with --enable-networking=lwip appropriately.
 The driver on the other side we put it in libcpu/m68k/mcf5225x and it got
 built in the library context of the librtemsbsp.a.
 The driver has only 2 references on lwip headers ...

 To the bsp:

 The bsp we have adopted from mcf52223 and have created it as a own
 bsp-target=mcf5225x also via the autoconfig/automake mechanism.
 In the bsp itself i have modified the bsp_get_CPU_clock_speed() and some
 improvements in the console driver and PIT2 timer interrupt.
 The bsp_start() we have defined as weak symbol so we don't have to touch
 the "empty" bsp_start() of rtems coz it's platform-circuit
 specific you know.

--

Comment:

 lwip is currently in its own repo and has better support. Closing.

--
Ticket URL: <http://devel.rtems.org/ticket/1712#comment:11>
RTEMS Project <http://www.rtems.org/>
RTEMS Project