From: "usecool" <usecool@gmail.com>
To: "ecos-discuss" <ecos-discuss@ecos.sourceware.org>
Cc: "ecos-devel" <ecos-devel@ecos.sourceware.org>
Subject: Fw: A problem about freebsd tcpip on lpc2290 and dm9000ep
Date: Wed, 24 Mar 2010 15:49:00 -0000 [thread overview]
Message-ID: <201003242349360657326@gmail.com> (raw)
In-Reply-To: <201003242346351666244@gmail.com>
Hello all!
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!
Brg
Jeff Liang
2010-03-24
parent reply other threads:[~2010-03-24 15:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201003242346351666244@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003242349360657326@gmail.com \
--to=usecool@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).