RE: [ECOS] x86 - redboot - networking - how do they interconnect

[Ron Kundla <rkundla at nband dot com>]

Gary,

I see what you mean. I tried to change my build to reflect a fixed address
in redboot (192.168.1.2) and a BOOTP address (192.168.1.3) for the
application. When I try to initiate the 'init_all_network_interfaces', I get
an error telling me that the device is not configured.

Is this configuration part of the Configuration Tool settings, or do I need
to write some code to create the device? Also, should I be calling this
before or after the scheduler has started? Does it make a difference?

Would it just be easier to add another intel adapter? Or rather move to
serial debug and leave the ethernet alone?

Thanks,
Ron


-----Original Message-----
From: Gary Thomas [mailto:gthomas@redhat.com]
Sent: Thursday, July 26, 2001 4:10 PM
To: Ron Kundla
Cc: eCos Mailing List (E-mail)
Subject: RE: [ECOS] x86 - redboot - networking - how do they
interconnect

> (1) When redboot has come up, it has already initialized the Ethernet with
> an IP address. When I type 'continue' to start the kernel and my
> application, do I still have to do 'init_all_network_interfaces' to start
> the networking code? I tried to do this and it rebooted my target machine.
> 

Yes.  The [logical] interfaces are separate.

Note: in order to use RedBoot via the network and have an eCos application
also use the network, one of them will have to be configured to use a static
IP since the two worlds (RedBoot and eCos) need to use different IP
addresses.