I tried with a zImage, here is what I'm getting :
barebox:/ bootz /dev/nand0.kernel.bb
invalid magic 0x00002018
And here the ls -l /dev/nand0.* output :
barebox:/ ls -l /dev/nand0.*
crw------- 393216 /dev/nand0.barebox.bb
crw------- 131072 /dev/nand0.bareboxenv.bb
crw------- 2883584 /dev/nand0.kernel.bb
crw------- 533200896 /dev/nand0.root.bb
crw------- 533667840 /dev/nand0.root
crw------- 2764800 /dev/nand0.kernel
crw------- 131072 /dev/nand0.bareboxenv
crw------- 307200 /dev/nand0.barebox
Here is how I did my kernel and root partitions, following this steps :
addpart /dev/nand0 300k(barebox)ro,128k(bareboxenv),2700k(kernel),-(root)
nand -a /dev/nand0.*
update -t kernel -d nand
update -t rootfs -d nand
Is there any specific command to erase the nand before flashing it ?
On Mon, Oct 17, 2011 at 10:31:38PM +0200, Kamel BOUHARA wrote:A raw image does not have any magic number you could check, so the bootu
> > 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 ???
command relies on the user passing the correct image.
Sorry, I meant the output of 'ls -l /dev/nand0.*' to check the sizes of
>
> 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
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 |