Re: [ECOS] RedBoot not able to reach network

["Gary D. Thomas" <gary dot thomas at mind dot be>]

On Tue, 2003-07-22 at 01:51, mohanlal jangir wrote:
> I have rebuild RedBoot for ARM Integrator board with ARM920t core module.
> While booting I do receive following messages at minicom
> 
> RedBoot> +FLASH configuration checksum error or invalid key
> Ethernet eth0: MAC address 00:02:b3:8c:8a:bb
> Can't get BOOTP info for device!
> 
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v2_0 - built 09:37:00, Jul 21 2003
> 
> Platform: INTEGRATOR (ARM 9)
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
> 
> RAM: 0x00000000-0x01000000, 0x0000bfe8-0x00edd000 available
> FLASH: 0x24000000 - 0x26000000, 256 blocks of 0x00020000 bytes each.
> RedBoot>
> 
> 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".
> 
> Any kind of help will be appreciated.
> 

Do you have a DHCP/BOOTP server available on your network?
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.

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.
 
-- 
Gary D. Thomas <gary.thomas@mind.be>


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