All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Add new NAND flash
Date: Sat, 02 Oct 2010 14:50:23 +0200	[thread overview]
Message-ID: <4CA72A8F.3090402@arcor.de> (raw)
In-Reply-To: <20101001145222.1b8a4377@udp111988uds.am.freescale.net>

Hi Scott

Am 01.10.2010 21:52, schrieb Scott Wood:
> On Fri, 1 Oct 2010 16:31:40 +0200
>> MT29F16G08CBABA
>> The NAND is connected (8 bit wide) to an iMX25 which is booting from 
>> NOR. So the NAND is only a mass storage device. I am able to read the ID 
>> of the chip.
>>
>> 2Ch 48h 04h 46h 85h
>>
> 
> According to http://patchwork.ozlabs.org/patch/60042/, this chip
> is supposed to have ID: 2C 48 00 26 89

Take a closer look at the table in the link. There is a MT29F16G08ABABA
with ID: "2C 48 00 26 89" and a MT29F16G08CBABA with ID: "2C 48 04 46
85". The second one is the one I have here. I have also a datasheet of
the chip here from where I copy & pasted the above ID. The ID gets read
correctly from the chip by u-boot NAND subsystem.

> Do you have a datasheet that says what it's supposed to be?
> 
> The bytes may be getting corrupted.  If you hack up the code to
> override the ID bytes with good ones, do you see any problems doing
> real I/O?

I tried that. If I run a "nand bad" command then it never returns and
keeps performing some actions on the NAND device as I can see with an
oscilloscope.

-- 
Matthias Wei?er

  reply	other threads:[~2010-10-02 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 14:31 [U-Boot] Add new NAND flash Matthias Weißer
2010-10-01 19:52 ` Scott Wood
2010-10-02 12:50   ` Matthias Weißer [this message]
2010-10-04 16:25     ` Scott Wood
2013-03-01  1:55       ` garyio
2013-03-05  1:04         ` Scott Wood

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=4CA72A8F.3090402@arcor.de \
    --to=weisserm@arcor.de \
    --cc=u-boot@lists.denx.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 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.