From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Q: Bad bits in Nand Write
Date: Thu, 16 Feb 2012 13:21:14 -0600 [thread overview]
Message-ID: <4F3D572A.9080500@freescale.com> (raw)
In-Reply-To: <CAJ2oMh+aFGNZOfxJpNXe55CjexAr3ykQjoAqo5pbvqjSJCv4_A@mail.gmail.com>
On 02/14/2012 09:05 AM, Ran Shalit wrote:
> Hello,
>
> I am using Micron Nand MT29F1G08ABC , with OMAP-L138 board, and I
> write the Nand with the following sequence in U-Boot:
> 1. erase block
> 2, read complete page change the first byte and then write back the
> complete page (2048 bytes)
> 3, read complete page change the next byte and then write back the
> complete page (2048 bytes)
> 4. back to 3. until page is written completely
>
> What I see is that after about ~1200 bytes, bytes which are after the
> last offset such as 1400 and 1500 offset are not 0xff but instead one
> of the bits is zero (such as 0xbf)
> What Do you think might be the problem here ...
Read the manual for your NAND chip -- this is almost certainly violating
the chip's specs. There's a limit on the number of partial programmings
that you can do to a page in between erases. 1, 4, and 8 are common
limits. 2048 is not.
-Scott
next prev parent reply other threads:[~2012-02-16 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 15:05 [U-Boot] Q: Bad bits in Nand Write Ran Shalit
2012-02-16 19:21 ` Scott Wood [this message]
2012-02-17 10:34 ` Ran Shalit
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=4F3D572A.9080500@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