public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Johannes Bauer <weolanwaybqm@spornkuller.de>,
	Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Wear-leveling peculiarities
Date: Tue, 26 May 2015 15:20:45 -0300	[thread overview]
Message-ID: <5564B97D.4090203@vanguardiasur.com.ar> (raw)
In-Reply-To: <fa1a37d3deb8876079963af7ddc0ff25@joe.dyn.spornkuller.de>

On 05/26/2015 08:14 AM, Johannes Bauer wrote:
> Am 26.05.2015 12:08, schrieb Richard Weinberger:
> 
>> What flash is this?
>> I should not start dying that early.
> 
> To be honest, I have no idea. The problem is that the CPU is stacked on
> top of the NAND via package-on-package technlogoly. The whole component
> is supplied by a third party (and I've just scanned their documentation,
> which does not give any hints about the origin of the NAND). So I have
> no markings on the package (POP) and no documentation. The only thing I
> do have is dmesg:
> 
> omap2-nand driver initializing
> ONFI flash detected
> NAND device: Manufacturer ID: 0x20, Chip ID: 0xaa (ST Micro NAND 256MiB
> 1,8V 8-bit)
> 

According to this:

http://www.linux-mtd.infradead.org/nand-data/nanddata.html

0x20 0xaa is the ID of Numonyx/ST NAND02GXXX. Searching for the specs it
seems the device is SLC, so it's kind of unexpected that the default WL
value was wrong.

> Maybe there's a way to talk to the NAND directly and get some more
> identification, but I don't know how. Any hints? I'd happily provide clues.
> 

The ONFI specs talk about that (a quick "onfi spec pdf" search will do).
The ONFI specifies a paramter page which contains all the information
about the device (5.7.1. Parameter Page Data Structure Definition).

Keep us updated if you find why the flashes are dying :)
-- 
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar

  parent reply	other threads:[~2015-05-26 18:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 13:53 Wear-leveling peculiarities Johannes Bauer
2015-05-18 14:09 ` Johannes Bauer
2015-05-18 17:58   ` Richard Weinberger
2015-05-18 17:59     ` Richard Weinberger
2015-05-18 20:38     ` Johannes Bauer
     [not found]     ` <555A4D38.3070702@spornkuller.de>
2015-05-18 20:47       ` Richard Weinberger
2015-05-26  9:38         ` Johannes Bauer
2015-05-26 10:08           ` Richard Weinberger
2015-05-26 11:14             ` Johannes Bauer
2015-05-26 16:19               ` Jeff Lauruhn (jlauruhn)
2015-05-26 16:24                 ` Johannes Bauer
2015-05-26 16:29                   ` Richard Weinberger
2015-05-26 18:20               ` Ezequiel Garcia [this message]
2015-05-19  9:17 ` valent.turkovic
2015-05-26  9:43   ` Johannes Bauer

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=5564B97D.4090203@vanguardiasur.com.ar \
    --to=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=weolanwaybqm@spornkuller.de \
    /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