From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks
Date: Wed, 20 Mar 2013 16:24:45 -0500 [thread overview]
Message-ID: <1363814685.25034.17@snotra> (raw)
In-Reply-To: <20130320212007.GL30773@bender.unx.csupomona.edu> (from henson@acm.org on Wed Mar 20 16:20:07 2013)
On 03/20/2013 04:20:07 PM, Paul B. Henson wrote:
> On Tue, Mar 19, 2013 at 06:23:27PM -0500, Scott Wood wrote:
>
> > > I don't think this is having any functional impact, as the scrub
> > > component of burning a new nand image wipes out the bad blocks,
> >
> > You should not be routinely scrubbing NAND!
> >
> > The manufacturers put bad block information there for a reason.
>
> Hmm, I was following the instructions in doc/README.mx28_common, which
> says to use "run update_nand_full" to burn the NAND image, and one
> component of that per include/configs/mx28evk.h is:
>
> nand scrub -y 0x0 ${filesize}
>
> Are the instructions/env script incorrect?
The env script is incorrect. Otavio, Marek, what's going on here?
> I don't believe the bad blocks that linux finds are actual bad blocks,
> and definitely not factory bad blocks. They seem to show up as a
> byproduct of the way u-boot is burning the NAND image. They are always
> at the same addresses (I tried two different NAND chips), and only
> appear when u-boot is used to burn the bootstream, but not when
> kobs-ng
> is used.
My guess is there's some mismatch regarding NAND layout, but someone
more familiar with mx28 will need to answer that...
-Scott
next prev parent reply other threads:[~2013-03-20 21:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 0:50 [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks Paul B. Henson
2013-03-19 23:23 ` Scott Wood
2013-03-20 21:20 ` Paul B. Henson
2013-03-20 21:24 ` Scott Wood [this message]
2013-04-04 10:09 ` Trent Piepho
2013-04-06 4:28 ` Paul B. Henson
2013-04-06 7:18 ` Trent Piepho
2013-04-11 0:20 ` Paul B. Henson
2013-04-11 12:03 ` Trent Piepho
2013-04-11 18:33 ` Paul B. Henson
2013-04-11 23:25 ` Trent Piepho
2013-04-20 1:03 ` Paul B. Henson
2013-04-20 1:22 ` Trent Piepho
2013-04-23 0:42 ` Paul B. Henson
2013-04-26 1:13 ` Marek Vasut
2013-04-29 20:54 ` Paul B. Henson
2013-04-29 21:01 ` Marek Vasut
2013-05-04 0:08 ` Marek Vasut
2013-05-04 6:21 ` Trent Piepho
2013-05-04 13:20 ` Marek Vasut
2013-04-13 14:42 ` Marek Vasut
2013-04-13 16:31 ` Trent Piepho
2013-04-13 18:26 ` Marek Vasut
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=1363814685.25034.17@snotra \
--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