This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM355 Nandflash and Uboot problem

hi, everyone,

      This morning I download an new kernel 2.6.18 and make it as an uImage use the default 355config, also I have't notice it's larger than the old one, so I have't change the bootargs, when the filesize is 1.5M but the new one is 1.9M, so I got an problem like follow:

Time: timer0_1 clocksource has been installed.
Clock event device timer0_0 configured with caps set: 08
Switched to high resolution mode on CPU 0
yaffs: dev is 32505859 name is "mtdblock3"
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
nand_davinci_4bit_compare_ecc Too many errors to be corrected!
nand_davinci_4bit_compare_ecc Too many errors to be corrected!

……

nand_davinci_4bit_compare_ecc Too many errors to be corrected!
nand_davinci_4bit_compare_ecc Too many errors to be corrected!

 

when I reboot use the old one, it also got an problem like :

yaffs: dev is 32505859 name is "mtdblock3"
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
block 1 is bad
block 2 is bad
block 3 is bad
block 4 is bad
block 5 is bad
block 6 is bad
block 7 is bad

……


block 4093 is bad
block 4094 is bad
block 4095 is bad
block 4096 is bad
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 180K
Warning: Cannot create /dev/console: -2Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

 

so, does some one meet this too? what should I do?

                                                        thanks to all