Did you have any bad blocks during the erase? U-boot isn't smart enough
to deal with bad blocks ... I have a board that has one in the middle of
the kernel image. I moved it away from the bad block and changed the
nboot address to match.
Steve
Joshua Hintze wrote:
Hello,
I am having trouble boot from NAND flash larger images. Previously my
kernel uImage was around 1.4 megs. I just recently enabled some other
options and it grew in size to 1.6 megs.
Our nand flash layout is like this...
0x00000000-0x00018000 : "UBL image"
0x00018000-0x00044000 : "U-boot image"
0x00044000-0x00208000 : "Kernel image"
0x00208000-0x003ffc000 : "JFFS2"
So we have more than enough space. I load the uImage into ram using
tftpboot and then nand erase/nand write it out making sure I write all
of it and erase enough space.
However when I go to boot it I get the following:
Loading from device 0: <NULL> at 0x2000000 (offset 0x44000)
Image Name: Linux-2.6.10_mvl401-davinci_evm
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1646412 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
## Booting image at 80700000 ...
Image Name: Linux-2.6.10_mvl401-davinci_evm
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1646412 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... Bad Data CRC
However, if I just bootm after I loaded it with tftpboot it works just
fine. So there is some problem in the reading/writing to the NAND flash.
Any thoughts?
Thanks,
Josh
------------------------------------------------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
