NAND Boot Issue
Sascha Hauer
s.hauer at pengutronix.de
Tue Oct 18 02:58:10 EDT 2011
On Mon, Oct 17, 2011 at 10:31:38PM +0200, Kamel BOUHARA wrote:
> > bootu is for starting raw kernel images. Do you have such an image?
> > Normally you have an uImage (bootm) or a zImage (bootz)
>
>
> Ok so that maybe the solution because I didn't tried with the bootm .... my
> bad ! But why did I don't have the "Bad magic number" error like when I
> tried the boot command ???
A raw image does not have any magic number you could check, so the bootu
command relies on the user passing the correct image.
>
> Here is the ls /dev result:
>
> barebox:/ ls /dev/
> zero defaultenv mem
> nor0 nand0 nand_oob0
> ram0 phy0 self_raw
> self0 env_raw env0
> nor0.barebox nor0.bareboxenv nor0.kernel
> nor0.root nand0.barebox nand0.bareboxenv
> nand0.kernel nand0.root nand0.root.bb
> nand0.kernel.bb nand0.bareboxenv.bb nand0.barebox.bb
Sorry, I meant the output of 'ls -l /dev/nand0.*' to check the sizes of
your partitions.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list