[U-Boot] Problem with Kernel and u-boot interface

[Ramesh V]

Hi all,



[Background]

We are porting latest u-boot version and linux kernel (2.6.31) for our
PPC440 based customized board.



[Console Log]

### main_loop: bootcmd="bootm 0xffdc0000 - 0xff200000"


Hit any key to stop autoboot:  0


## Current stack ends at 0x1fec9d10


*  kernel: cmdline image address = 0xffdc0000


## Booting kernel from Legacy Image at ffdc0000 ...


   Image Name:   Linux-2.6.31


   Image Type:   PowerPC Linux Kernel Image (gzip compressed)


   Data Size:    1005412 Bytes = 981.8 kB


   Load Address: 00000000


   Entry Point:  00000000


   kernel data at 0xffdc0040, len = 0x000f5764 (1005412)


## Skipping init Ramdisk


## No init Ramdisk


   ramdisk start = 0x00000000, ramdisk end = 0x00000000


*  fdt: cmdline image address = 0xff200000


## Checking for 'FDT'/'FDT Image' at ff200000


*  fdt: raw FDT blob


## Flattened Device Tree blob at ff200000


   Booting using the fdt blob at 0xff200000


   of_flat_tree at 0xff200000 size 0x00003000


   Uncompressing Kernel Image ... OK


   kernel loaded at 0x00000000, end = 0x0020e034


## initrd_high = 0x30000000, copy_to_ram = 1


   ramdisk load start = 0x00000000, ramdisk load end = 0x00000000


## device tree at 0xFF200000 ... 0xFF202FFF (len=24576=0x6000)


   Loading Device Tree to 00ffa000, end 00ffffff ... OK


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

   Booting using OF flat tree ...



[Observation]

After printing the above log messages, system hangs.

It seems that kernel image and blob is loaded from flash to DDR and uboot
passes the control to the kernel. But not getting any messages from kernel
side.



#1. Kindly let us know, whether this is the problem with the kernel image or
device tree blob or uboot?

#2. Please let us know, how to start debugging the kernel after u-boot
passes the control to Kernel ?



Thanks in advance.



Thanks and Regards,

Ramesh Velusamy.