This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: A problem about freebsd tcpip on lpc2290 and dm9000ep
- From: John Dallaway <john at dallaway dot org dot uk>
- To: usecool <usecool at gmail dot com>
- Cc: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Sat, 27 Mar 2010 10:35:44 +0000
- Subject: [ECOS] Re: A problem about freebsd tcpip on lpc2290 and dm9000ep
- References: <201003242346351666244@gmail.com>, <201003242349360657326@gmail.com> <201003271152144536786@gmail.com>
Hi Jeff
usecool wrote:
> I am using eCos V3.0 on my lpc2290 board.
> My board have 2MB nor FLASH(0x80000000), 1MB SRAM(0x81000000),
> DM9000EP(0x83000000, IRQ is EINT0).
> I modify the phycore229x's bsp for my board, now it works.
> But , i meet a problem, when it power on, I can ping the board, TTL is 1-2ms.
> A TCP server thread for echo received data, it worked well.
> After several minutes, I ping the board, it will no reply
> or the TTL over 1000ms. I use wireshark catch the packets, I find
> the PC send arp request,but the board no arp replay, or replay pack
> will delay above 20~30seconds, The TCP thread worked deviant also.
> But same time ,the timer, TTY worked well.
> can anyone help me? Thanks!
A common cause of large _TCP_ delays is that the configured maximum
number of open sockets (CYGPKG_NET_MAXSOCKETS for eCos FreeBSD stack)
has been exceeded. Note that socket resources are not released for
re-use until some considerable time (2*MSL) after a socket is closed.
This doesn't explain all the behaviour you report, but worth mentioning...
John Dallaway
eCos maintainer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss