From: Steven Zedeck <saz@proliphix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
Date: Wed, 17 Feb 2010 07:38:27 -0800 (PST) [thread overview]
Message-ID: <27625639.post@talk.nabble.com> (raw)
In-Reply-To: <20100216183514.GA26893@loki.buserror.net>
Scott Wood-2 wrote:
>
> On Fri, Feb 12, 2010 at 06:14:51PM -0800, Steven Zedeck wrote:
>> Its in board/atmel/at91sam9rlek/nand.c
>>
>> It doesn't do much but set up the various GPIO connections. Here's the
>> function:
>>
>> 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;".
>
> -Scott
>
>
Scott,
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
CFG_NAND_DBW_8 is set in my configs.h file.
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
That comes from nand_bbt.c
Clearly there is something I'm missing regarding how the BBT is created and
utilized in Uboot.
thanks,
Steve
--
View this message in context: http://old.nabble.com/-PATCH--add-explicit-bbt-creation-to-commandline-tp18299804p27625639.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-02-17 15:38 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 [this message]
2010-02-17 19:10 ` Scott Wood
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=27625639.post@talk.nabble.com \
--to=saz@proliphix.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