Re: [ECOS] RedBoot not able to reach network

["mohanlal jangir" <mohanlaljangir at hotmail dot com>]

> On Tue, 2003-07-22 at 01:51, mohanlal jangir wrote:
> > I have rebuild RedBoot for ARM Integrator board with ARM920t core
module.
> > RedBoot is able to detect the network card I have in one of the PCI
slots. I
> > am able to configure address also but can not ping to other machines on
> > network. Even I can not ping to loop back address also. If I try to run
some
> > application with function build_boot_record for device eth0, I get error
> > message "IOCIFADDR: Device not configured".
> >
>
> Do you have a DHCP/BOOTP server available on your network?
No. I do not have any DHCP/BOOTP. But if I am configuring IP Address
manually using ip_address command, why should I need that.

> Are the BOOTP requests making it to the network?  This is crucial to
> know as BOOTP typically needs to be set up for each particular target
> system.
Actully this is one of the problems I am facing. I am running RedBoot on one
Intel x86 system also. I do see lot of BOOTP packets when this system boots
(of course, there are no replies for them, since I don't have any DHCP/BOOTP
server) but when my target boots I don't see any BOOTP packets. This is
forcing me to think that the RedBoot image I built is wrong. But I don't
know what mistake I did.

> If you update your eCos sources to the latest CVS, you'll find that
> RedBoot now performs a true DHCP discovery, as opposed to the simple
> BOOTP, which may work better for you.
>
I am having eCos v2_0. I think this should be ok.


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss