From: snijsure@grid-net.com (Subodh Nijsure)
To: linux-arm-kernel@lists.infradead.org
Subject: GPMI NAND on MX28 with DT.with
Date: Thu, 21 Jun 2012 15:24:25 -0700 [thread overview]
Message-ID: <4FE39F19.9090105@grid-net.com> (raw)
Has anyone gotten the latest GPMI NAND patches for MX28 with device-tree
to work?
I came across this thread where Huang Shijie reported that it has some
issues with ECC.
Our attempt to attach fail as shown below, anybody else encountered
these errors?
cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00020000 "boot"
mtd1: 0f200000 00020000 "data"
mtd2: 00400000 00020000 "boot-config"
ubiformat /dev/mtd1
ubiformat: mtd1 (nand), size 253755392 bytes (242.0 MiB), 1936
eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 1935 -- 100 % complete
ubiformat: 1933 eraseblocks have valid erase counter, mean value is 3
ubiformat: 3 bad eraseblocks found, numbers: 264, 468, 1593
ubiformat: formatting eraseblock 1935 -- 100 % complete
/ # ubiattach /dev/ubi_ctrl -m 1
[ 185.560000] UBI error: vtbl_check: bad CRC at record 0: 0x2b4f6dd5,
not 0x000000
[ 185.560000] UBI error: vtbl_check: bad CRC at record 0: 0x2b4f6dd5,
not 0x000000
[ 185.560000] UBI error: process_lvol: both volume tables are corrupted
[ 185.560000] UBI error: ubi_attach_mtd_dev: failed to attach mtd1,
error -22
ubiattach: error!: cannot attach mtd1
error 22 (Invalid argument)
-Subodh Nijsure
next reply other threads:[~2012-06-21 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:24 Subodh Nijsure [this message]
2012-06-22 14:45 ` GPMI NAND on MX28 with DT.with Huang Shijie
2012-07-03 15:00 ` Lauri Hintsala
2012-07-03 15:14 ` Huang Shijie
2012-07-04 5:19 ` Lauri Hintsala
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=4FE39F19.9090105@grid-net.com \
--to=snijsure@grid-net.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).