NAND Boot Issue

[Kamel BOUHARA]

> 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 ???

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



2011/10/17 Sascha Hauer <s.hauer at pengutronix.de>

> On Mon, Oct 17, 2011 at 06:03:56PM +0200, Kamel BOUHARA wrote:
> > Hi all,
> >
> > Im working on my own imx27 designed board and wanted to try barebox on
> > it.Actually I'm trying it with the phytec board config and it seems to
> work
> > fine booting on my nfs kernel and rootfs.
> > But when Im trying to boot from my 128MiB NAND memory then it doesn't
> work
> > and there is no decompression stage from the kernel.
> > Here is what Im getting :
> >
> > Board: Phytec phyCard-i.MX27
> > registered netconsole as cs1
> > cfi_probe: cfi_flash base: 0xc0000000 size: 0x02000000
> > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xac (Micron NAND 512MiB
> 1,8V
> > 8-bit)
> > Bad block table found at page 262080, version 0x01
> > Bad block table found at page 262016, version 0x01
> > Before PHY reset
> > After PHY reset
> > ULPI Vendor ID 0xffffff92    Product ID 0xffffff92
> > No ISP1504 found
> > ehci at ehci0: USB EHCI 1.00
> > ULPI Vendor ID 0xffffff92    Product ID 0xffffff92
> > No ISP1504 found
> > ehci at ehci1: USB EHCI 1.00
> > Malloc space: 0xa7a00000 -> 0xa7f00000 (size  5 MB)
> > Stack space : 0xa79f8000 -> 0xa7a00000 (size 32 kB)
> > running /env/bin/init...
> >
> > Hit any key to stop autoboot:  1
> > booting kernel of type uImage from /dev/nand0.kernel.bb
> > barebox:/ bootu /dev/nand0.kernel.bb
>
> bootu is for starting raw kernel images. Do you have such an image?
> Normally you have an uImage (bootm) or a zImage (bootz)
>
> > commandline: console=ttymxc0,115200 video=imxfb:Chimei-LW700AT9003
> > arch_number: 1698
> >
> > It seems I'm getting some issues with my nand since when I tried to flash
> it
> > and the erase task failed :
> >
> > erasing partition /dev/nand0.kernel.bb
> >
> > erase: Invalid argument
>
> Works here. I can't see how erase could return -EINVAL. can you please
> post the output of 'ls /dev/nand0*'?
>
> 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 |
>



-- 
__________________________________
*Kamel BOUHARA*
7 rue Jules César
02100 SAINT-QUENTIN
06.17.83.29.04
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/barebox/attachments/20111017/75583a58/attachment.html>