Hi, I have the same problem! What you do exactly to make the kernel boot? The Add_uboot_boot_entry is very long!
I have loaded jsff2 and kernel in NAND. 2008/12/5 rams <[EMAIL PROTECTED]>: > > Hi Berger, > > Thank you very much buddy > for the immediate reply. > It helped me a lot. > Please add in wiki so it will > help many people. > > Loading Android :). > > Thanks, > Ram. > > On Dec 5, 11:29 pm, "Cédric Berger" <[EMAIL PROTECTED]> wrote: >> You have to modify u-boot env : >> seehttp://lists.openmoko.org/nabble.html#nabble-td1458397 >> (and search wiki. some examples of using setenv >> :http://wiki.openmoko.org/wiki/Booting_from_SD#Add_uboot_boot_entry) >> >> | Andy Green wrote: >> >> |> Somebody in the thread at some point said: >> |> | Latest uImage-android seems to be broken - uboot gives Bad data CRC >> |> | message with it. >> |> | Can anybody post some older uImage-android ? >> |> >> |> No this is caused by U-Boot's default environment only pulling in 2MB >> |> from the NAND partition for kernel. Increase it like this -> >> |> >> |> setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand >> |> read.e 0x32000000 kernel 0x300000\; bootm 0x32000000 >> |> saveenv >> >> On Fri, Dec 5, 2008 at 14:58, rams <[EMAIL PROTECTED]> wrote: >> > NAND read: device 0 offset 0x80000, size 0x200000 >> > 2097152 bytes read: OK >> > ## Booting kernel from Legacy Image at 32000000 ... >> > Image Name: Linux-2.6.28-rc4-mokodev >> > Created: 2008-12-03 13:25:40 UTC >> > Image Type: ARM Linux Kernel Image (uncompressed) >> > Data Size: 2491904 Bytes = 2.4 MB >> > Load Address: 30008000 >> > Entry Point: 30008000 >> > Verifying Checksum ... Bad Data CRC >> > ERROR: can't get kernel image! > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
