From: Kamel BOUHARA <k.bouhara@gmail.com>
To: barebox@lists.infradead.org
Subject: Fwd: Nand MTD IOError -5
Date: Tue, 19 Jul 2011 18:40:35 +0200 [thread overview]
Message-ID: <CAM9uW_5koAxxk8Jgqe7_sEzCd0FNzb7d=KOBTaayT6GvqOMhhA@mail.gmail.com> (raw)
In-Reply-To: <CAM9uW_7ynAvvm_y_k0LiO5dzkuji1i4CYJvn6pZ7heNeQ6P=5A@mail.gmail.com>
[-- 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
prev parent reply other threads:[~2011-07-19 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:21 Kamel BOUHARA
2011-07-18 6:44 ` Sascha Hauer
[not found] ` <CAM9uW_7ynAvvm_y_k0LiO5dzkuji1i4CYJvn6pZ7heNeQ6P=5A@mail.gmail.com>
2011-07-19 16:40 ` Kamel BOUHARA [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM9uW_5koAxxk8Jgqe7_sEzCd0FNzb7d=KOBTaayT6GvqOMhhA@mail.gmail.com' \
--to=k.bouhara@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox