From: Brendan J Simon <brendan.simon@bigpond.com>
To: ecos-discuss <ecos-discuss@sourceware.cygnus.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>
Subject: Re: [ECOS] ecos: TCP/UDP/IP with Linux simulator
Date: Wed, 31 Jan 2001 19:08:00 -0000 [thread overview]
Message-ID: <3A78D315.2000902@bigpond.com> (raw)
In-Reply-To: <3A78C982.1965F29F@redhat.com>
Jonathan Larmour wrote:
> Brendan J Simon wrote:
>
>> I am designing a mobile robot with a wireless interface. It will
>> communicate via TCP/UDP/IP to a server on a Linux host. I want to
>> simulate all the robot software (including ecos with the tcp/udp/ip
>> stack) with ecos linux simulator.
>> Is this possible ?
>> Will the tcp/udp/ip interface simuate properly ?
>> Do I have to write some kind of dummy/simulation driver for the wireless
>> interface ?
>
> The TCP stack cannot be simulated on the linux synthetic target yet. As I
> think you are hinting at, it is possible to write a "driver" that could use
> linux system calls to communicate with an external process, so that eCos
> thinks it is talking to an ethernet card when it isn't really. But no-one
> has done that yet.
>
> And out of interest, eCos would require work to be ported to credit card
> sized PCs - the eCos PC port cannot be put into flash yet.
Looks like I'll stick to the powerpc MPC555 or MPC850 boards that I have
found. I'm sure it wont be hard to port these since there are other
850/555 boards in eCos.
With regards to the TCP/IP thing, I'm sure I can conjour up something.
Why can't the TCP/IP stack be simulated ?? The only thing I think you
would need would be simulated physical drivers (eg. ethernet).
Thanks,
Brendan Simon.
next prev parent reply other threads:[~2001-01-31 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 17:50 Brendan J Simon
2001-01-31 18:27 ` Jonathan Larmour
2001-01-31 19:08 ` Brendan J Simon [this message]
2001-01-31 19:12 ` Jonathan Larmour
2001-02-01 9:30 ` Donnat Eric
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=3A78D315.2000902@bigpond.com \
--to=brendan.simon@bigpond.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.com \
/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).