All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Vikram Narayanan <vikram186@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>, linux-mtd@lists.infradead.org
Subject: Re: mtd_oobtest fails with GPMI-NAND
Date: Wed, 08 May 2013 16:33:12 +0200	[thread overview]
Message-ID: <518A6228.6050608@denx.de> (raw)
In-Reply-To: <510CB507.4020105@gmail.com>

Hi Vikram,

I might be seeing something similar on my iMX6 board. Here
mtd_subpagetest sometimes fails.

What is the current status on your platform? Did you resolve this
problem? If yes, what did you have to change/fix?

Thanks,
Stefan

On 02/02/2013 07:41 AM, Vikram Narayanan wrote:
> On 1/30/2013 7:57 AM, Huang Shijie wrote:
>> 于 2013年01月30日 00:28, Vikram Narayanan 写道:
>>> On 1/29/2013 8:06 AM, Huang Shijie wrote:
>>>>> May I know in what way the driver is restricted for using with other
>>>>> boards?
>>>> The devicetree. Please check the dts file in arch/arm/boot/dts/.
>>>> If there is no dts file for your board, the gpmi will not works very
>>>> well for your board.
>>>> for example, there is arch/arm/boot/dts/imx6q-arm2.dts for the MX6Q-ARM2
>>>> board.
>>>
>>> I've a valid dts file for my board which is good enough to probe the
>>> Toshiba NAND on-board and mount a UBIFS filesystem.
>> could you tell the dts file for your board?
>> are you sure the pinmux settings are right?
> 
> I'm using the same pinumx settings mentioned in the file
> "arch/arm/boot/dts/imx6q.dtsi". Hope that is right.
> 
>>>
>>>>> You're right and we knew it earlier as the Kernel detects the OOB size
>>>>> as 128 bytes. So, some remaining bytes become unused at the end of
>>>>> each page. i.e., (224-128). Instead of supporting ecc strength as ECC9
>>>>> we end up using ECC8. Should this be a cause for the -74 error?
>>>> no. this is not the cause. even you get the wrong geometry of the nand
>>>> chip. the gpmi still can works.
>>>>
>>>> I think the root cause is the devicetree issue as above.
>>>
>>> Something else is causing the issue. Can you give some other pointers
>>> which can potentially cause this -74 error while mounting?
>> the -74 error is the EBADMSG, it's caused by the uncorrectable ECC failure.
>> There are many reasons can cause this error:
>>     [1] the pinmux setting is not right, the gpmi does not works well.
> 
> As said above, my pinmux settings are right. GPMI detects my NAND, does 
> read/write/erase/mount. At times I'm seeing this -74 issue. Sometimes 
> this error goes off in the next reboot.
> 
>>     [2] the wrong setting of BCH. for example, the page size is 8K, you
>> set 4k to BCH.
>>         so you can set the correct nand geometry parameters for your
>> nand chip firstly, and then do the debug.
> 
>  From the driver I understood that the geometry are determined according 
> to the data from the read_id bytes. mtd layer detects my NAND as 4K 
> page-sized. So, this shouldn't be a problem I guess.
> 
>>     [3] timings.
> 
> Should I tweak something specific according to the NAND device that I 
> have? Can you give more hints please?
> 
> Thanks,
> Vikram
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

  parent reply	other threads:[~2013-05-08 14:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 16:52 mtd_oobtest fails with GPMI-NAND Vikram Narayanan
2013-01-21  2:12 ` Huang Shijie
2013-01-28  2:39   ` Vikram Narayanan
2013-01-28  3:20     ` Huang Shijie
2013-01-28 17:04       ` Vikram Narayanan
2013-01-29  2:06         ` Huang Shijie
2013-01-29  2:26           ` Vikram Narayanan
2013-01-29  2:36             ` Huang Shijie
2013-01-29 16:28               ` Vikram Narayanan
2013-01-30  2:27                 ` Huang Shijie
2013-02-02  6:41                   ` Vikram Narayanan
2013-02-02  7:42                     ` Huang Shijie
2013-02-02  7:46                       ` Huang Shijie
2013-05-08 14:33                     ` Stefan Roese [this message]
2013-05-09 12:30                       ` Vikram Narayanan
2013-05-10  6:20                         ` Stefan Roese
2013-05-12 12:10                           ` Vikram Narayanan
2013-05-12 15:09                             ` Stefan Roese
2013-05-13 16:38                               ` Vikram Narayanan
2013-05-13  2:51                           ` Huang Shijie
2013-05-13  8:01                             ` Stefan Roese
2013-05-13  9:01                               ` Huang Shijie
2013-05-13  9:22                                 ` Stefan Roese
2013-05-13  9:34                                   ` Huang Shijie
2013-05-13 10:02                                     ` Stefan Roese
2013-05-14  2:09                                       ` Huang Shijie
2013-05-14  2:11                                       ` Huang Shijie
2013-05-13 16:51                                 ` Vikram Narayanan
2013-05-14  2:23                                   ` Huang Shijie
2013-05-14  2:33                                     ` Vikram Narayanan
2013-05-14  2:47                                       ` Huang Shijie
2013-05-13 16:43                               ` Vikram Narayanan

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=518A6228.6050608@denx.de \
    --to=sr@denx.de \
    --cc=b32955@freescale.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vikram186@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.