From: syed riyaz <forriyaz@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: mtd nand issue
Date: Mon, 26 Jan 2009 05:08:29 -0800 (PST) [thread overview]
Message-ID: <15731.47945.qm@web63005.mail.re1.yahoo.com> (raw)
Hi I use a 2K page size 1 GB nand chip on a mx31 ads basd board. At redboot level, read and write happpen perfectly. Even in kernel, flash_eraseall is fine. Then i did nanddump -p and saw 0xff on all addresses. So i believe the nand driver is fine.I am trying to use a nand partition as my rootfilesystem. I have partioned nand into 4 mtd blocks. 60 MB for the first 3 and and the remaining 820 in the 4th block. I created a 8 MB jffs2 file system named rootfs.jffs2 with the proper erase size. Wrote to mtd block 6 usingnandwrite /dev/mtd/6 rootfs.jffs2When linux mounted this block, i went in fine for the first time. But subsequent booting returned lot of CRC errors until the file system was hopelessly currupted. Any help appreciated.The messages are likemtd->read:0x100 bytes from block 0 CRC error.I read somewhere that the factory information about bad blocks is stores in first block and if erased will lead to errors. Pleas elaborate if you know.Please
answer my queries so i understand things a litle better.1) Is it ok to flash a 8 MB image on a 60 MB partion. Are the errors because the remaining partition doesnt match?2) If i specify "root=/dev/mtdblock6" while booting, does the kernel see only mtd7 as available space or will mtd5 and mtd7 and mtd8 will also be available as user space.3)What does nandwrite -a -p mean?
Thanking you
next reply other threads:[~2009-01-26 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 13:08 syed riyaz [this message]
2009-01-28 12:30 ` mtd nand issue Nils Faerber
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=15731.47945.qm@web63005.mail.re1.yahoo.com \
--to=forriyaz@yahoo.com \
--cc=linux-mtd@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