Hi All,

I am trying to bring up Linux on EST8260 board. U-boot has come up and I was able to run some example program that comes along with U-boot. But when I am trying to boot linux I am getting the following messages. (Debug flag has been enabled).

################################################### U-Boot 1.0.0 (Jan 3 2004 - 13:04:45)

BOOTP broadcast 1

got BOOTP packet (src=67, dst=68, len=300 want_len=300)

Filtering pkt = 0

Bootfile: uImage

Got good BOOTP

TFTP from server 192.168.15.219; our IP address is 192.168.15.222

Filename 'uImage'.

Load address: 0x400000

Loading: *#################################################################

##########################################

done

Bytes transferred = 547323 (859fb hex)

## Booting image at 00400000 ...

Image Name: Linux Kernel Image

Created: 2004-01-03 8:03:00 UTC

Image Type: PowerPC Linux Kernel Image (gzip compressed)

Data Size: 547259 Bytes = 534.4 kB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

Uncompressing Kernel Image ... OK

## Current stack ends at 0x03F77878 => set upper limit to 0x00800000

## cmdline at 0x007FFF00 ... 0x007FFF7E

bd address = 0x03F77FB4

memstart = 0x00000000

memsize = 0x04000000

flashstart = 0x40000000

flashsize = 0x00400000

flashoffset = 0x00023000

sramstart = 0x00000000

sramsize = 0x00000000

immr_base = 0x0F000000

bootflags = 0x00000001

vco = 132 MHz

sccfreq = 33 MHz

brgfreq = 33 MHz

intfreq = 198 MHz

cpmfreq = 66 MHz

busfreq = 33 MHz

ethaddr = 00:A0:1E:A8:7B:CB

IP addr = 192.168.15.222

baudrate = 9600 bps

No initrd

## Transferring control to Linux (at address 00000000) ...

###############################################

I was going through the mailing list and I found that many have faced similar problem. I am using Linux 2.4.22. I tried almost all the options like changing the baudrate, setting and unsetting the clocks_in_mhz variable, etc. The bd_info structure definition is same both in Linux kernel tree and U-boot source. The variables CFG_IMMR and IMAP_ADDR are also similar. I even tried with a ramdisk image, then also the kernel hangs at the same place. Is incorrect SDRAM initialization a cause for this problem? Any sort of help in this regard will be hugely appreciated.

thanks in advance... regards, Sudhakar.

__________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003