Hi Unnamalai,
But upon booting kernel through u-boot, after inflation, I only get the message 'Starting kernel ...' and the system hangs.
Well control has passed to the linux kernel, so you need to start diagnosing Linux - U-Boot works fine now ;)
The log as under:
====================================================================== $bootm 83a00000 ## Booting kernel from Legacy Image at 83a00000 ... Image Name: Linux Created: 2010-06-25 9:13:44 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 2611097 Bytes = 2.5 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
==========================================================================
The 'bootargs' env variable is
bootargs= root=/dev/nfs nfsroot=10.100.144.245:/android/android_rootfs,nolock,rsize=1024,wsize=1024 ip=10.100.144.42:10.100.144.245::255.255.255.0::eth0:on console=ttyS2,115200 init=/init mem=64M comm_v75 uart_dma android
Any further clues on what could be wrong for kernel not getting booted?
Is the "console" setting correct? I.e. are you connected to ttyS2? Does U-Boot pass the correct machine number (check with bdinfo) for the kernel you use?
If you can reset the board at this time, you can try to inspect the kernel logbuffer for output which Linux produced but which never reached your serial connection:
http://www.denx.de/wiki/view/DULG/LinuxPostMortemAnalysis
Cheers Detlev