Booting new MPC5200B board

I'm using OSELAS-tiny-5 to compile a kernel for my new Phytec
5200B-tiny board with u-boot. When I try booting the kernel via tftpd
I get this error about the RAMDisk. Why does it want a RAMDisk, and
how do I supply it with one?

uboot> run bcmd_net
Using FEC ETHERNET device
TFTP from server 192.168.1.4; our IP address is 192.168.1.11
Filename 'uImage-pcm030'.
Load address: 0x500000
Loading: #################################################################
         #################################################################
         #################################################################
         ###########################################
done
Bytes transferred = 1215281 (128b31 hex)
Using FEC ETHERNET device
TFTP from server 192.168.1.4; our IP address is 192.168.1.11
Filename 'oftree-pcm030.dtb'.
Load address: 0x400000
Loading: #
done
Bytes transferred = 5091 (13e3 hex)
## Booting image at 00500000 ...
   Image Name:   Linux-2.6.20-rt3-pcm030-4
   Created:      2007-08-17  19:20:07 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1215217 Bytes =  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00000000 ...
Bad Magic Number


-- 
Jon Smirl
jonsmirl@gmail.com

On 8/17/07, Jon Smirl [off-list ref] wrote:

I'm using OSELAS-tiny-5 to compile a kernel for my new Phytec
5200B-tiny board with u-boot. When I try booting the kernel via tftpd
I get this error about the RAMDisk. Why does it want a RAMDisk, and
how do I supply it with one?

The problem with the RAMDisk error is caused by the board shipping
with uboot 1.1.4. Upgrading to 1.2.0 fixes it.

1.1.4 doesn't implement dtb support
 bootm 0x500000 - 0x400000
gets interpreted as load a RAM disk at 00000.

-- 
Jon Smirl
jonsmirl@gmail.com