public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Enabling nand createbbt command
Date: Thu, 8 Mar 2012 15:08:32 -0600	[thread overview]
Message-ID: <4F591FD0.8020705@freescale.com> (raw)
In-Reply-To: <FD2DBC0E1365154BB0E3E348680BA0E902A1BF24@nzc-ap-xch-03.ap.trimblecorp.net>

On 03/08/2012 03:01 PM, Bud Miljkovic wrote:
> 
>> -----Original Message-----
>> From: Scott Wood [mailto:scottwood at freescale.com]
>> Sent: Friday, 9 March 2012 9:02 a.m.
>> To: Bud Miljkovic
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] Enabling nand createbbt command
>>
>>
>> It should happen automatically when nand_erase_opts() calls
>> chip->scan_bbt(), provided the driver set the NAND_USE_FLASH_BBT flag,
>> and that NAND_BBT_CREATE/NAND_BBT_WRITE are set in the nand_bbt_descr
>> (this is the case if the driver doesn't override the default
>> nand_bbt_descr).
>>
>> Are you not seeing it happen?  What version of U-Boot are you using,
>> with which NAND controller driver?
> 
> I am using u-boot-2009.08 sources from Freescale released under SABRE
> Automotive Infotainment board aka mx53_ard.

Please use a recent upstream U-Boot, or contact support at freescale.com
for support with your Freescale-supplied code.

> Looking at this from the u-boot commands prospective,
> - I get "nand - NAND sub-system" but it does not recognize "nand
> createbbt" command

Is there a reason you're expecting it to exist?

> I am fairly newbee in this and would not know which NAND controller
> driver is used.

Why are you using the scrub command?  It's an "I know what I'm doing"
backdoor.  There's even a warning, with confirmation prompt, telling you
it's dangerous and to only use it "if you are sure of what you are doing".

-Scott

  parent reply	other threads:[~2012-03-08 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  1:56 [U-Boot] Enabling nand createbbt command Bud Miljkovic
2012-03-08 16:54 ` Scott Wood
2012-03-08 19:38   ` Bud Miljkovic
2012-03-08 20:02     ` Scott Wood
     [not found]       ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF24@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 21:08         ` Scott Wood [this message]
2012-03-08 21:22           ` Bud Miljkovic
2012-03-08 21:41             ` Fabio Estevam
     [not found]               ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF27@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 22:44                 ` Fabio Estevam
     [not found]                   ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF2A@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 23:03                     ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2012-03-08 22:08 Bud Miljkovic
2012-03-08 23:01 Bud Miljkovic
2012-03-08 23:10 ` Fabio Estevam
2012-03-09  0:58 Bud Miljkovic
2012-03-11 19:19 ` Charles Manning
2012-03-14  4:00   ` Bud Miljkovic
2012-03-14 17:23     ` Charles Manning
2012-03-18 23:09       ` Bud Miljkovic
2012-03-19 21:56         ` Charles Manning

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=4F591FD0.8020705@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