From: Grant Erickson <marathon96@gmail.com>
To: "Ghorai, Sukumar" <s-ghorai@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Grazvydas Ignotas <notasas@gmail.com>,
Charles Manning <manningc2@actrix.gen.nz>
Subject: Re: No more software ECC in omap2.c NAND driver. Why?
Date: Sun, 21 Nov 2010 22:39:10 -0800 [thread overview]
Message-ID: <C90F500E.2033D%marathon96@gmail.com> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B0369C42A32@dbde02.ent.ti.com>
On 11/21/10 10:27 PM, Ghorai, Sukumar wrote:
>> -----Original Message-----
>> From: Grant Erickson [mailto:marathon96@gmail.com]
>> Sent: Monday, November 22, 2010 11:39 AM
>> To: Charles Manning
>> Cc: linux-omap@vger.kernel.org; Grazvydas Ignotas; Ghorai, Sukumar
>> Subject: Re: No more software ECC in omap2.c NAND driver. Why?
>>
>> On 11/21/10 1:01 PM, Charles Manning wrote:
>>> Just recompiling with the CONFIG_MTD_NAND_OMAP_HWECC define commented
>> out did
>>> not result in a working system. I suspect there is more tto the problem
>> than
>>> this.
>>
>> FWIW, I had the exact same issues with my Mistral AM37x EVM board. I not
>> only had to remove/deassert CONFIG_MTD_NAND_OMAP_HWECC, but also had to
>> roll
>> back nand_base.c and nand_bbt.c back to their 2.6.32 versions (later ones
>> between .32 and .35 might have worked but I didn't bother trying) to be
>> able
>> to read, error-free and correctly, NAND that was erased and written with a
>> .32-era kernel.
>
> [Ghorai] are you trying again?
> How do you flush the FS (form u-boot or from kernel, nandwrite)? And let me
> know the test you are doing, to know the steps to reproduce in my platform -
> zoom/sdp.
The board (Mistral AM37x) NAND (Micron 256 MiB) was originally bootstrapped
over SD/MMC from u-boot using the following script:
mmc init
mw.b ${loadaddr} 0xff 0x40000
nand erase 0 0x40000
fatload mmc 0 ${loadaddr} mlo
nandecc hw
nand write.i ${loadaddr} 0 0x40000
mw.b ${loadaddr} 0xff 0x180000
nand erase 0x00040000 0x180000
nand erase 0x001c0000 0x180000
fatload mmc 0 ${loadaddr} u-boot.bin
nandecc sw
nand write.i ${loadaddr} 0x00040000 0x180000
nand write.i ${loadaddr} 0x001c0000 0x180000
mw.b ${loadaddr} 0xff 0x800000
nand erase 0x00400000 0x800000
nand erase 0x03a00000 0x800000
fatload mmc 0 ${loadaddr} uImage
nand write.i ${loadaddr} 0x00400000 0x800000
nand write.i ${loadaddr} 0x03a00000 0x800000
mw.b ${loadaddr} 0xff 0x2000000
nand erase 0x00c00000 0x2000000
nand erase 0x04200000 0x2000000
fatload mmc 0 ${loadaddr} root.jff
nand write.i ${loadaddr} 0x00c00000 0x2000000
nand write.i ${loadaddr} 0x04200000 0x2000000
Following that, the board is updated, from Linux, using 'flash_eraseall -q'
and 'nandwrite -p -q' on all partitions, except that containing MLO.
Best,
Grant
next prev parent reply other threads:[~2010-11-22 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 1:06 No more software ECC in omap2.c NAND driver. Why? Charles Manning
2010-11-18 14:33 ` Ghorai, Sukumar
2010-11-19 10:35 ` Grazvydas Ignotas
2010-11-19 20:45 ` Ghorai, Sukumar
2010-11-21 21:01 ` Charles Manning
2010-11-22 6:08 ` Grant Erickson
2010-11-22 6:27 ` Ghorai, Sukumar
2010-11-22 6:39 ` Grant Erickson [this message]
2010-11-22 7:29 ` Ghorai, Sukumar
2010-11-22 19:03 ` Grant Erickson
2010-11-24 14:08 ` Ghorai, Sukumar
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=C90F500E.2033D%marathon96@gmail.com \
--to=marathon96@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
--cc=notasas@gmail.com \
--cc=s-ghorai@ti.com \
/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