How to make u-boot boot the kernel?

I have a 128Mb board , I was able to compile and install u-boot without any
issues. The problem i'm facing is the kernel loads but never boots. 

Excerpt
"
## Booting kernel from Legacy Image at 32000000 ...
   Image Name:
   Created:      2010-02-09  12:25:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2041256 Bytes =  1.9 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
"

How to make the linux kernel boot? 

But if I use tftpboot to load the kernel the linux kernel boot and starts
loading.
Settings for  bootcmd are bootargs 
"
bootcmd=nboot.e kernel ; bootm
bootargs=noinitrd console=ttySAC0,115200 root=/dev/mtdblock3
rootfstype=jffs2 rw
 mini2440=3tb
"

When the kernel starts booting via tftpboot i get the following errors
"
->read(0x400 bytes from 0x420000) returned ECC error
jffs2_scan_eraseblock(): Node at 0x00420000 {0x1985, 0xe000, 0x00000029)
has invalid CRC 0x60046646 (calculated 0x1c7375c8)
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00420004:
0x0029 instead
"

Can anyone explain as to what is going on..

regards

First thing: mini2440=3tb  is that the parameter VGA?

Are you loading in a fresh JFFS2 image or modifying something in your JFFS2
fs then re-booting?

I have noticed the first time I boot a fresh JFFS2 image everything is
fine, but if I modify anything and re-boot then I get CRC errors, but it
still works properly.

Yours does look different to the error I get, but . . .

HTH

hi davef
3tb is for the newer 240by340  displays. The kernel does support it. 

I'm loading a fresh jffs2 file. No modifications . 

regards

A longshot, but have you made your own rootfs?  I am wondering if these
errors are showing up as the rootfs is being mounted.

If you have made you own rootfs have you tested it?

http://wiki.maemo.org/Modifying_the_root_image

and use the second mount_jffs2.sh

After you have loaded the kernel there is a test you can do, which is
suppose to give you some idea of whether or not the kernel is working.

***
After you have loaded the kernel you can try the following test:

  nand read 0x31000000 kernel 0x500000
  bootm 0x31000000

You should observe that the kernel gets further through the boot process,
possibly to the place where the file system would try to mount.
***

If this is happy proceed with loading in your rootfs.

Where have you compiled your kernel from? And what 2.6.xx.x is it.