public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 22 Nov 2010 11:03:56 -0800	[thread overview]
Message-ID: <C90FFE9C.203C0%marathon96@gmail.com> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B0369C42AB7@dbde02.ent.ti.com>

On 11/21/10 11:29 PM, Ghorai, Sukumar wrote:
>> The board (Mistral AM37x) NAND (Micron 256 MiB) was originally
>> bootstrapped
>> over SD/MMC from u-boot using the following script:
>
> [Ghorai] let me know the nand details - x8/x16, small/big page?

It's the Micron 256 MiB x16 2 KiB page size, 128 KiB erase block size device
on the Mistral AM37x board.

>>     fatload mmc 0 ${loadaddr} root.jff
>
> [Ghorai] How you create the root.jff
> mkfs.jffs2 --output=root.jffs2 --root=.. --pagesize=?? --eraseblock=?? -n

% mkfs.jffs2 --little-endian --no-cleanmarkers --pad 2048 --pagesize 2048
--eraseblock 131072 -d /tmp/tmp.h9dKGpcNFw -D root.devices -o root.jffs2

>>     nand write.i ${loadaddr} 0x00c00000 0x2000000
>>     nand write.i ${loadaddr} 0x04200000 0x2000000
>
> [Ghorai] why you writing in two places?

Redundant images.

>> Following that, the board is updated, from Linux, using 'flash_eraseall -
>> q'
>> and 'nandwrite -p -q' on all partitions, except that containing MLO.
> [Ghorai] 
>
> 1. can you send the exact comment you used to write in nand? Which partition?

    flash_eraseall -q /dev/mtd7
    nandwrite -p -q /dev/mtd7 root.jffs2
    flash_eraseal -q /dev/mtd9
    nandwrite -p -q /dev/mtd9 root.jffs2

> 2. What is the last kernel you used and was working perfectly?

v2.6.32_OMAPPSP_03.00.01.06.patch1

Best,

Grant



  reply	other threads:[~2010-11-22 19:04 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
2010-11-22  7:29           ` Ghorai, Sukumar
2010-11-22 19:03             ` Grant Erickson [this message]
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=C90FFE9C.203C0%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