mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Gabriel Tisan <gabriel.tisan@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: imx35_nand driver
Date: Mon, 30 Apr 2012 14:29:55 +0200	[thread overview]
Message-ID: <CAD9ZU8Cbsa0L5rgBudy7ADwgrxNrrsRPf_qx=PdrQCRJvvmrxA@mail.gmail.com> (raw)
In-Reply-To: <20120427142310.GG17184@pengutronix.de>

>> Hi !
>>
>> I try to upgrade a custom board from an old version(2009) of barebox
>> to a new one.
>>
>> But I have some problems when the nand driver is
>> loading(imx35_add_nand(&nand_info)
>>
>> After I boot with the old barebox, I use tftp to load the new version
>> of barebox in ram and at run I get this on console :
>>
>> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB
>> 3,3V 8-bit)
>> Bad block table not found for chip 0
>> Bad block table not found for chip 0
>> Scanning device for bad blocks
>> Bad eraseblock 0 at 0x00000000
>> Bad eraseblock 1 at 0x00020000
>> Bad eraseblock 2 at 0x00040000
>> ................
>>
>> It seems that it could not find the bad block tables, although on the
>> old barebox they are found.
>>
>> Has someone an idea what I could try to go forward ?
>
> Not a good idea. Some things to check:
>
> have you played with the nand clock in your board setup (IMX_CCM_BASE +
> CCM_PDR4)?
No. I have almost the same board setup like freescale-mx35-3-stack

> do you pass hw_ecc = 1 to the nand driver? I think this was the same
> back in 2009, but I don't really know.
Yes. I use this :
struct imx_nand_platform_data nand_info = {
	.hw_ecc		= 1,
	.flash_bbt	= 1,
};

bbt_pattern has also not changed from 2009.

However thanks !

Gabriel

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2012-04-30 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 10:39 Gabriel Tisan
2012-04-27 14:23 ` Sascha Hauer
2012-04-30 12:29   ` Gabriel Tisan [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='CAD9ZU8Cbsa0L5rgBudy7ADwgrxNrrsRPf_qx=PdrQCRJvvmrxA@mail.gmail.com' \
    --to=gabriel.tisan@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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