This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ecos: TCP/UDP/IP with Linux simulator
- To: ecos-discuss <ecos-discuss at sourceware dot cygnus dot com>
- Subject: Re: [ECOS] ecos: TCP/UDP/IP with Linux simulator
- From: Brendan J Simon <brendan dot simon at bigpond dot com>
- Date: Thu, 01 Feb 2001 14:08:05 +1100
- CC: Jonathan Larmour <jlarmour at redhat dot com>
- References: <3A78C0C7.5040403@bigpond.com> <3A78C982.1965F29F@redhat.com>
- Reply-To: brendan dot simon at bigpond dot 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.