From: Alexander Aring <alex.aring@gmail.com>
To: Vanhauwaert Wouter <W.Vanhauwaert@TELEVIC.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: NAND + imx53, BBT/timings?
Date: Fri, 14 Jun 2013 09:02:15 +0200 [thread overview]
Message-ID: <20130614070213.GA13398@x61s.8.8.8.8> (raw)
In-Reply-To: <E78BBE677EB9144B8F0A0A29674CD5338ECF0A3DAA@SRV-VS06.TELEVIC.COM>
Hi,
On Thu, Jun 13, 2013 at 09:09:11AM +0200, Vanhauwaert Wouter wrote:
> Hi all,
>
> I'm working on a custom design which has an imx53 and a 1GB NAND flash (Samsung k9k8g08u0d) via an 8 bit bus.
> So I added this imx_nand_platform_data structure with a .width=1, .hw_ecc=1 and .flash_bbt=1.
> The flash gets detected at startup (also loads the bootloader from it).
>
> nand: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit), page size 2048, OOB size:64
> but then
> nand: Bad block table not found for chip 0
> nand: Bad block table not found for chip 0
>
> etc
>
> and when I do imx_nand_bbm, I get:
> Bad eraseblock 0 at 0x00000000
> Bad eraseblock 1 at 0x00020000
> And for the rest UnCorrectable RS-ECC errors
>
> This is a barenew flash, so I suppose I should find a factory bad block table?
No, this is a another bad block table. [1] You need to generate the bbt.
Factories only marks block as bad(with an mark pattern).
> I'm using the barebox 2013.05.1 stable release from git
>
You can "try" to generate a bbt when you generate a nand bad block aware
device, nand command "nand -a", then run "nandtest -t -m /dev/nand#.bb" to fill
this bbt with "current" badblocks.
I don't know if this generates a bbt for you. But give it a try, I think
it should do :/
[1] http://www.linux-mtd.infradead.org/tech/mtdnand/x144.html
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-06-14 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 7:09 Vanhauwaert Wouter
2013-06-14 7:02 ` Alexander Aring [this message]
2013-10-09 8:55 ` Vanhauwaert Wouter
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=20130614070213.GA13398@x61s.8.8.8.8 \
--to=alex.aring@gmail.com \
--cc=W.Vanhauwaert@TELEVIC.com \
--cc=barebox@lists.infradead.org \
/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