From: micro1183 <micro1183@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] Add support for Micron MT29F8G08 8Gb NAND flash MID: 0x2c, DID: 0x38
Date: Thu, 12 Dec 2013 09:38:08 +0100 [thread overview]
Message-ID: <52A975F0.2000002@gmail.com> (raw)
In-Reply-To: <1386807878.10013.226.camel@snotra.buserror.net>
On 12/12/2013 01:24 AM, Scott Wood wrote:
> On Wed, 2013-12-11 at 22:16 +0100, micro1183 wrote:
>> On 12/11/2013 06:22 PM, Scott Wood wrote:
>>> On Wed, 2013-12-11 at 12:02 +0100, micro1183 wrote:
>>>> Microns MT29F8G08 8GBit flash is not identified correctly.
>>>> Manufacturer ID is 0x2c, device ID is 0x38
>>>>
[snip]
>>>>
>>>
>>> Is this an ONFI flash? If so, use that instead of the ID table.
>>>
>>> -Scott
>>>
>>
>> Hi Scott,
>>
>> yes it's an ONFI flash, but the OOB size is 224 bytes, which results in
>> a data abort (see below).
>>
>> Apparently the supported ONFI detected OOB sizes are 8,16,64 and 128 bytes.
>> I lack a nand_oob_224 struct but I don't know what the default positions
>> would be.
>
> What NAND driver are you using? Are you using hardware ECC or software
> ECC?
I use the omap nand driver, the cpu is a AM335x with hw ecc elm.
Depending on the flash type, the rom code expects BCH8 or BCH16 unless
ECC is completely disabled.
I'm not sure if the ecc hw is used but I see oob bytes being used. How
can I verify this?
--Lo
next prev parent reply other threads:[~2013-12-12 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 11:02 [U-Boot] [RFC PATCH] Add support for Micron MT29F8G08 8Gb NAND flash MID: 0x2c, DID: 0x38 micro1183
2013-12-11 17:22 ` Scott Wood
2013-12-11 21:16 ` micro1183
2013-12-12 0:24 ` Scott Wood
2013-12-12 8:38 ` micro1183 [this message]
2013-12-12 19:12 ` 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=52A975F0.2000002@gmail.com \
--to=micro1183@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox