From: Robert Brusa <bob.brusa@gmail.com>
To: "Simon Kallweit" <simon.kallweit@intefo.ch>
Cc: "MailingList:ecos-discuss ;" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS]How to run testprograms for lwip
Date: Thu, 23 Jul 2009 12:19:00 -0000 [thread overview]
Message-ID: <op.uxisichskeg3uf@localhost> (raw)
In-Reply-To: <4A6835B0.6000803@intefo.ch>
On Thu, 23 Jul 2009 12:04:32 +0200, Simon Kallweit
<simon.kallweit@intefo.ch> wrote:
> Robert Brusa wrote:
>> Hi
>> I have included the package lwip_tcpip in my library and now I want to
>> run
>> the test programs that come with it. But how? Take e.g. tcpecho. I built
>> it using my library, then download it into my at91sam7x256-based board
>> and
>> run it. Nothing happens. What should happen? What "special actions" am I
>> supposed to do? Thanks for help.
>
> Do you see any diagnostic output on the serial port?
>
> TCP echo test will simply echo everything that's sent to the open test
> port. You can for example use telnet or netcat to send some strings to
> the device and get the echo responses.
>
> Simon
Hi Simon
yes, I see some messages on ser1. It appears every few seconds, but I get
the impression there is no answer comming back. I also hooked my PC to the
LAN with wireshark and there as well, I see nothing originating from my
board.
tcpecho: When attempting to connect to my board (where tcpecho is running)
with telnet 192.168.0.222 I get the message
telnet: Unable to connect to remote host: No route to host
I have the feeling its a hardware problem. The LEDs on the switch I am
connected to with this board also remain dark all the time.
Robert
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-07-23 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 9:50 Robert Brusa
2009-07-23 10:02 ` Simon Kallweit
2009-07-23 12:19 ` Robert Brusa [this message]
2009-07-23 12:25 ` Simon Kallweit
2009-07-24 15:51 ` Robert Brusa
2009-07-29 12:25 ` Sergei Gavrikov
2009-07-29 12:32 ` Simon Kallweit
2009-07-30 9:11 David Fernandez
2009-07-30 11:02 ` Sergei Gavrikov
2009-07-30 11:11 ` Simon Kallweit
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=op.uxisichskeg3uf@localhost \
--to=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=simon.kallweit@intefo.ch \
/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).