From: Kamel BOUHARA <k.bouhara@gmail.com>
To: barebox@lists.infradead.org
Subject: Nand MTD IOError -5
Date: Fri, 15 Jul 2011 13:21:21 +0200 [thread overview]
Message-ID: <CAM9uW_7pYJS1jzPxcCPphPgMi=ckstKm8=_6dsrCRn3Bp-sCXw@mail.gmail.com> (raw)
[-- 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
next reply other threads:[~2011-07-15 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:21 Kamel BOUHARA [this message]
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
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_7pYJS1jzPxcCPphPgMi=ckstKm8=_6dsrCRn3Bp-sCXw@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