Hello, all.

My goal is to succesfully pass a 2.6.26 linux kernel to the MPC5200B using the three-argument command bootm.

I'm using the DENX ELDK toolchain, the U-Boot v1.2.0, the dtc-v1.2.0 (latest device tree compiler), and a suitable tftp-server pointing to /tftpboot/5200.

I've built the image using the make ARCH=powerpc zImage command. It creates the cuImage.lite5200b along with the lite5200.dts (which I've compiled to a lite5200.dtb using the above mentioned dtc).

The bootloader stalls after uncompressing the kernel image. Check the snippet below after I've configured the bootloader (using GtkTerm for PC-board communications):

=> tftp 0x01000000 ${bootfile}

Using FEC ETHERNET device TFTP from server 192.168.1.100; our IP address is 192.168.1.101 Filename '5200/uImage'. Load address: 0x1000000

Loading: ################################################################# ############################ done Bytes transferred = 1352689 (14a3f1 hex) => bootm 0x01000000 - ${fdtaddr}

## Booting kernel from Legacy Image at 01000000 ... Image Name: Linux-2.6.26.8-dirty Created: 2009-01-21 14:33:22 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1352625 Bytes = 1.3 MB Load Address: 00400000 Entry Point: 00400550 Verifying Checksum ... OK

## Flattened Device Tree blob at 00040000 Booting using the fdt blob at 0x40000 Uncompressing Kernel Image ... OK

Please notice that the 5200/uImage (renamed from cuImage.lite5200b) is the bootfile. The fdtaddr bears the device tree blob address at 0x00040000.

One of my doubts is that I'm unsure to where the device tree and the image addresses should be. Obviously they should not overwrite each other, and that is exactly what I take care of when assigning the addresses' values. Still, I'm experiencing these stalls.

Any help would be highly appreciated.

Marco Antônio Possamai

Universidade Federal de Santa Catarina