mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* Nand MTD IOError -5
@ 2011-07-15 11:21 Kamel BOUHARA
  2011-07-18  6:44 ` Sascha Hauer
  0 siblings, 1 reply; 3+ messages in thread
From: Kamel BOUHARA @ 2011-07-15 11:21 UTC (permalink / raw)
  To: barebox


[-- Attachment #1.1: Type: text/plain, Size: 2827 bytes --]

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

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)
Bad block table found at page 262080, version 0x01

Bad block table found at page 262016, version 0x01

nand_read_bbt: Bad block at 0x01ac0000

nand_read_bbt: Bad block at 0x01ae0000

nand_read_bbt: Bad block at 0x01b40000

nand_read_bbt: Bad block at 0x01b60000

nand_read_bbt: Bad block at 0x02bc0000

nand_read_bbt: Bad block at 0x02be0000

nand_read_bbt: Bad block at 0x03240000

nand_read_bbt: Bad block at 0x03260000

nand_read_bbt: Bad block at 0x033c0000

nand_read_bbt: Bad block at 0x033e0000

nand_read_bbt: Bad block at 0x03f40000

nand_read_bbt: Bad block at 0x03f60000

nand_read_bbt: Bad block at 0x03fc0000

nand_read_bbt: Bad block at 0x03fe0000

nand_read_bbt: Bad block at 0x057c0000

nand_read_bbt: Bad block at 0x057e0000

nand_read_bbt: Bad block at 0x05ac0000

nand_read_bbt: Bad block at 0x05ae0000

nand_read_bbt: Bad block at 0x05bc0000

nand_read_bbt: Bad block at 0x05be0000

nand_read_bbt: Bad block at 0x07440000

nand_read_bbt: Bad block at 0x07460000

nand_read_bbt: Bad block at 0x078c0000

nand_read_bbt: Bad block at 0x078e0000

nand_read_bbt: Bad block at 0x07cc0000

nand_read_bbt: Bad block at 0x07ce0000

nand_read_bbt: Bad block at 0x134c0000

nand_read_bbt: Bad block at 0x134e0000

nand_read_bbt: Bad block at 0x14940000

nand_read_bbt: Bad block at 0x14960000

nand_read_bbt: Bad block at 0x15540000

nand_read_bbt: Bad block at 0x15560000

nand_read_bbt: Bad block at 0x15ac0000

nand_read_bbt: Bad block at 0x15ae0000

nand_read_bbt: Bad block at 0x17140000

nand_read_bbt: Bad block at 0x17160000

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 ?

Regards.

-- 
__________________________________
*Kamel BOUHARA*
7 rue Jules César
02100 SAINT-QUENTIN
06.17.83.29.04

[-- Attachment #1.2: Type: text/html, Size: 9273 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Nand MTD IOError -5
  2011-07-15 11:21 Nand MTD IOError -5 Kamel BOUHARA
@ 2011-07-18  6:44 ` Sascha Hauer
       [not found]   ` <CAM9uW_7ynAvvm_y_k0LiO5dzkuji1i4CYJvn6pZ7heNeQ6P=5A@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Sascha Hauer @ 2011-07-18  6:44 UTC (permalink / raw)
  To: Kamel BOUHARA; +Cc: barebox

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 |

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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Fwd: Nand MTD IOError -5
       [not found]   ` <CAM9uW_7ynAvvm_y_k0LiO5dzkuji1i4CYJvn6pZ7heNeQ6P=5A@mail.gmail.com>
@ 2011-07-19 16:40     ` Kamel BOUHARA
  0 siblings, 0 replies; 3+ messages in thread
From: Kamel BOUHARA @ 2011-07-19 16:40 UTC (permalink / raw)
  To: barebox


[-- Attachment #1.1: Type: text/plain, Size: 3155 bytes --]

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


2011/7/18 Sascha Hauer <s.hauer@pengutronix.de>
>
>> 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@pengutronix.de>

> 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

[-- Attachment #1.2: Type: text/html, Size: 5491 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-07-19 16:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-15 11:21 Nand MTD IOError -5 Kamel BOUHARA
2011-07-18  6:44 ` Sascha Hauer
     [not found]   ` <CAM9uW_7ynAvvm_y_k0LiO5dzkuji1i4CYJvn6pZ7heNeQ6P=5A@mail.gmail.com>
2011-07-19 16:40     ` Fwd: " Kamel BOUHARA

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox