From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip
Date: Tue, 3 Jan 2012 16:08:33 -0600 [thread overview]
Message-ID: <4F037C61.6020508@freescale.com> (raw)
In-Reply-To: <CAPBSBxr=HRmxN2VdytJpZbEfHrSYr7=9Q_HP817gqNBJHeDsUA@mail.gmail.com>
On 01/03/2012 03:48 PM, Matthew L. Creech wrote:
> On Sat, Dec 3, 2011 at 11:31 PM, <shuo.liu@freescale.com> wrote:
>> From: Liu Shuo <shuo.liu@freescale.com>
>>
>> Freescale FCM controller has a 2K size limitation of buffer RAM. In order
>> to support the Nand flash chip whose page size is larger than 2K bytes,
>> we read/write 2k data repeatedly by issuing FIR_OP_RB/FIR_OP_WB and save
>> them to a large buffer.
>
> (Starting a new thread so I don't hijack your patch)
>
>
> Hi Scott / Liu,
>
> We're using the MPC8313 and booting from a 2k NAND (using a SPL
> image). Like others, we're a bit concerned about continued
> availability of 2k parts. So this change -- being able to use the FCM
> with a 4k chip -- would be very useful to us.
>
> However, so far all of the 4k chips that we've seen have a higher
> error rate than our current 2k chips. Therefore they all recommend
> that something stronger than 1-bit ECC is used. Since the FCM only
> supports 1-bit ECC in hardware, it implies that we'll need to use
> software BCH to utilize a 4k chip.
Even on SLC chips, when using an ECC block size of 512 bytes? Or are
you only able to find MLC?
I looked for a datasheet for a 4K NAND chip, but couldn't find one
readily available from a Google search. Hopefully someone internally
can provide me with the one for the chip we're using.
> But this seems like it's going to pose problems when we build U-Boot:
> the SPL boot code is already heavily trimmed down to make it squeeze
> into the requisite 4k, so it seems unlikely that we can add software
> BCH support and remain within that size limit.
There's also the issue of ECC on the boot page itself -- that has to be
hardware ECC, because there's no software running yet.
> If using the U-Boot SPL: are you using a 4k part that works with just
> 1-bit ECC? (If so, which one?) Or are you using 1-bit ECC for
> U-Boot, then BCH for the remainder of flash? (This seems dangerous
> for long-term usage, if errors accumulate in the blocks containing
> U-Boot)
AFAIK, we've just been using 1-bit hw ECC. I don't know what NAND chip
was used for testing, or how much stress testing was done.
-Scott
next prev parent reply other threads:[~2012-01-03 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 21:48 [U-Boot] [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip Matthew L. Creech
2012-01-03 22:08 ` Scott Wood [this message]
2012-01-03 22:43 ` Matthew L. Creech
2012-01-03 23:58 ` Scott Wood
2012-01-04 16:09 ` Matthew L. Creech
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=4F037C61.6020508@freescale.com \
--to=scottwood@freescale.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