This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: TCP/IP and rom startup mode
- To: Fano dot Ramparany at rd dot francetelecom dot fr
- Subject: Re: [ECOS] TCP/IP and rom startup mode
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Fri, 18 May 2001 20:28:25 +0100
- Cc: eCos Disuss <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <3B053E1F.6A479A35@rd.francetelecom.fr>
Fano Ramparany wrote:
>
> I'm using TCP/IP stack in a client application running on eCos (the
> server runs
> on a unix workstation). When running the client in "RAM startup" mode
> (mode for debugging) everything works fine.
> When running it in "ROM startup" mode I've noticed the following
> problems:
> 1- it takes about one minute for the function
> "init_all_network_interfaces" to complete.
> whereas in "RAM startup" mode although it takes some time for gdb to
> download
> the client code on the board, once done,
> "init_all_network_interfaces" completes
> immediately.
It sounds like maybe BOOTP/DHCP is timing out. Except I don't know why this
would be specific to ROM startup. Perhaps something else in this area of
your configuration changed?
> 2- I can establish a socket connection with the bootp server (the
> argument
> of the tcpconnection function) only. If I my server runs on another
> unix workstation,
> my client can't connect to it
Perhaps it needs routing?
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine