Fwd: Nand MTD IOError -5

[Kamel BOUHARA <k.bouhara@xxxxxxxxx>]

---------- Forwarded message ----------
From: Kamel BOUHARA <k.bouhara@xxxxxxxxx>
Date: 2011/7/19
Subject: Re: Nand MTD IOError -5
To: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>

2011/7/18 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>

On Fri, Jul 15, 2011 at 01:21:21PM +0200, Kamel BOUHARA wrote:
> Hello,
>
> Im having a trouble with my Nand Flash device wich is a 512MiB Micron with
> 4GB capacity.
> I get io error -5 for any erase/write operation on it like this :
>
>  barebox@Phytec phyCard-i.MX27:/ update -t barebox -d nand

Is this really a phycard or have you just used it as a template for your
board?

No, it's not Im using it as a template because the fec,  I've also post for it here :http://lists.infradead.org/pipermail/barebox/2011-July/003802.html

Sorry, no idea. It just looks there are quite many bad blocks. Does it
work under Linux?

It doesn't work on Linux or u-boot, same error,  maybe I missed somethink, I will look to make it work on u-boot with advanced nand command first maybe...

Thanks anyway ! :/

 

2011/7/18 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>

On Fri, Jul 15, 2011 at 01:21:21PM +0200, Kamel BOUHARA wrote:
> Hello,
>
> Im having a trouble with my Nand Flash device wich is a 512MiB Micron with
> 4GB capacity.
> I get io error -5 for any erase/write operation on it like this :
>
>  barebox@Phytec phyCard-i.MX27:/ update -t barebox -d nand

Is this really a phycard or have you just used it as a template for your
board?

>
> phy0: Link is up - 100/Full
> host 192.168.0.2 is alive
> > erasing partition /dev/nand0.barebox.bb
> >
> erase: I/O error
>
> flashing barebox.bin to /dev/nand0.barebox.bb
> TFTP from server 192.168.0.2 ('barebox.bin' -> '/dev/nand0.barebox.bb')
>         write: I/O error
> tftp failed: error -5
> And here is the device init at the boot runtime:
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xac (Micron NAND 512MiB 1,8V
> 8-bi)
>

> nand_read_bbt: Bad block at 0x17840000
>
> nand_read_bbt: Bad block at 0x17860000
>
> nand_read_bbt: Bad block at 0x1f0c0000
>
> nand_read_bbt: Bad block at 0x1f0e0000
>
> nand_read_bbt: Bad block at 0x1f6c0000
>
> nand_read_bbt: Bad block at 0x1f6e0000
>
> So it seems tge device is detect and bbt are correctly calculated...
> Any idea of what could be the problem ?

Sorry, no idea. It just looks there are quite many bad blocks. Does it
work under Linux?

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

-- 
__________________________________
Kamel BOUHARA

7 rue Jules César

02100 SAINT-QUENTIN
06.17.83.29.04

_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox