Latest andy-tracking , bad crc error
andy at openmoko.com
Sat Feb 28 12:22:07 CET 2009
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
| On Sat, 2009-02-28 at 10:14 +0100, Petr Vanek wrote:
|>> I checkout a latest kernel (andy-tracking), and compile the kernel,
|>> then flash to the FreeRunner.
|>> During booting, it says Bad data CRC. I have tried twice, I don't think
|>> usb tranfer erro. Before flashing the uImage, all is OK. What's the
|>> BTW, I flash back to original uImage, it works.
|> i think you have to either use qi or adjust uboot_env to be able to
|> load kernel image larger then 2M.
|> iirc boot_env could also be flashed if there was an image online -
|> perhaps somebody uploaded it already somewhere?
| Thanks pointing me to the right direction.
| I think I got it.
| Old u-boot might be NOT support uImage larger than 2M.
| I need to update u-boot (Nand) to support uImage(>2MB).
| If my understanding is wrong, please correct me. thanks.
No Petr's explanation is right, it is not U-Boot binary that is broken
but the "U-Boot environment" commands that explain the booting procedure.
We set it to pull in the first 2MB of the kernel only then jump to the
start of it.
Now kernels are >2MB, you get only part of the kernel image and then bad
CRC is true.
In Qi, the private bootloader environment concept is removed so this
situation should not be possible.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-kernel