From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
Date: Wed, 17 Feb 2010 13:10:48 -0600 [thread overview]
Message-ID: <4B7C3F38.2030707@freescale.com> (raw)
In-Reply-To: <27625639.post@talk.nabble.com>
Steven Zedeck wrote:
> Scott Wood-2 wrote:
>> On Fri, Feb 12, 2010 at 06:14:51PM -0800, Steven Zedeck wrote:
>>> int board_nand_init(struct nand_chip *nand)
>>> {
>>> nand->ecc.mode = NAND_ECC_SOFT;
>>> #ifdef CFG_NAND_DBW_16
>>> nand->options = NAND_BUSWIDTH_16;
>>> #endif
>>> nand->cmd_ctrl = at91sam9rlek_nand_hwcontrol;
>>> nand->dev_ready = at91sam9rlek_nand_ready;
>>> nand->chip_delay = 20;
>>>
>>> return 0;
>>> }
>> Add "nand->options |= NAND_USE_FLASH_BBT;".
[snip]
> I really appreciate your help. I added what you suggested, except since we
> are using an 8 bit wide bus and not 16 I had to do the following:
>
> #ifdef CFG_NAND_DBW_8
> nand->options |= NAND_USE_FLASH_BBT;
> #endif
I don't see why the ifdef is needed -- just don't put it inside (or
before) the other ifdef.
> Now when my board boots I get this and then it just stops:
> NAND: Entering nand_init
> Nand Base 0x40000000
> Bad block table not found for chip 0
> Bad block table not found for chip 0
The messages are expected on the first boot -- but it should then create
the bad block table.
You'll have to debug to find out why it's hanging. If you don't set
NAND_USE_FLASH_BBT, does ordinary nand read/write from the u-boot prompt
work?
-Scott
prev parent reply other threads:[~2010-02-17 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 8:04 [U-Boot-Users] [PATCH] add explicit bbt creation to commandline Harald Welte
2008-07-06 11:16 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-06 13:31 ` Wolfgang Denk
2008-07-07 18:39 ` Scott Wood
2010-02-12 2:49 ` [U-Boot] " Steven Zedeck
2010-02-12 17:04 ` Scott Wood
2010-02-12 17:38 ` Steven Zedeck
2010-02-12 17:48 ` Scott Wood
2010-02-12 18:47 ` Steven Zedeck
2010-02-12 18:53 ` Scott Wood
2010-02-12 19:18 ` Steven Zedeck
2010-02-12 19:36 ` Steven Zedeck
2010-02-12 21:23 ` Scott Wood
2010-02-13 2:14 ` Steven Zedeck
2010-02-16 18:35 ` Scott Wood
2010-02-17 15:38 ` Steven Zedeck
2010-02-17 19:10 ` Scott Wood [this message]
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=4B7C3F38.2030707@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.