Hi there,

I did the same but now also i get error...


U-Boot 1.3.3 (Jul 10 2008 - 16:33:09)

OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle Board + LPDDR/NAND
DRAM:  128 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Audio Tone on Speakers  ... complete
Hit any key to stop autoboot:  0
reading uImage

693740 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name:   Linux-2.6.29-omap1-g9985b01-dirt
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1956720 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!


Plz help!!!!!!!!!!!!!!!

On Tue, Sep 15, 2009 at 4:58 PM, Jim Huang <jserv...@gmail.com> wrote:

>
> 2009/9/15 sanyanniesunney anniesunney <laurelsgal...@gmail.com>:
> > I get the following error when i am using the prebuilt images...
> > Plz help!
> >
>
> hi,
>
> From the below messages, it seems that you are using older bootloader.
>  For newer ones,
> u-boot should be set to take the file "uImage.bin" as Linux kernel
> image instead of "uImage".
> So, the solution is to rename file "uImage.bin" to "uImage" on your SD
> card, and then retry.
>
> Thanks,
> Jim Huang (jserv)
> http://0xlab.org/
>
> > Texas Instruments X-Loader 1.41
> > Starting OS Bootloader...
> >
> >
> > U-Boot 2008.10-rc2 (Oct  2 2008 - 09:02:46)
> >
> > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
> > OMAP3 Beagle board + LPDDR/NAND
> > DRAM:  128 MB
> > NAND:  256 MiB
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Hit any key to stop autoboot:  0
> > reading uImage
> >
> > ** Unable to read "uImage" from mmc 0:1 **
> > reading rd-ext2.bin
> >
> > ** Unable to read "rd-ext2.bin" from mmc 0:1 **
> > Wrong Image Format for bootm command
> > ERROR: can't get kernel image!
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to