lwip 1.3.1 testing

Simon Kallweit <[email protected]>
Newsgroups gmane.os.ecos.devel
Message-ID <[email protected]>
Hi

I have done a new lwip test release with the following changes:

* incorporated Sergei's patch (ctrl-c support)
* added an lwip_eth_simple and lwip_eth_sequential template

The new test release can be downloaded from 
http://download.westlicht.ch/lwip-20090825.tar.gz

To do synth tests do the following:

create a new configuration:
 > ecosconfig new linux lwip_eth_simple
or:
 > ecosconfig new linux lwip_eth_sequential

enable eth0 synth device (file is attached):
 > ecosconfig import eth_synth.ecm

build:
 > make
 > make -C build/net/lwip_tcpip/current tests

run tests (a sample target.tdf is attached):
./build/install/tests/net/lwip_tcpip/current/tests/httpd_simple -t 
target.tdf -io -nw

The current templates use DHCP to get an IP address. Just reconfigure 
for static IPs.

To do some stress testing you can run the nc_test_slave testcase (only 
available in sequential mode). You will need the corresponding master 
test, which can be found in the ecos repository under

packages/net/common/current/tests

To build the nc_test_master go to the upper directory and type:
 > make -f make.host

Also you should loosen up the very conservative default configuration of 
lwip pbufs to avoid dropped packets:

 > ecosconfig import pbufs.ecm
 > make && make -C build/net/lwip_tcpip/current tests



Testing on real hardware would be especially useful. Also testing on 
big-endian targets might reveal some issues, as I've only been testing 
on little-endian platforms.

Thanks a lot for testing!

Simon
eth_synth.ecm (text/plain, 63 B)
cdl_option CYGVAR_DEVS_ETH_ECOSYNTH_ETH0 {
    user_value 1
};
target.tdf (text/plain, 61 B)
synth_device ethernet {

    eth0 real eth1
    logging 0

}
pbufs.ecm (text/plain, 118 B)
cdl_option CYGNUM_LWIP_TCP_MSS {
    user_value 512
};

cdl_option CYGNUM_LWIP_PBUF_POOL_SIZE {
    user_value 64
};
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.