* imx35_nand driver
@ 2012-04-27 10:39 Gabriel Tisan
2012-04-27 14:23 ` Sascha Hauer
0 siblings, 1 reply; 3+ messages in thread
From: Gabriel Tisan @ 2012-04-27 10:39 UTC (permalink / raw)
To: barebox
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 ?
------------------------------------old
CONFIG-------------------------------------
CONFIG_NAND=y
CONFIG_NAND_IMX=y
CONFIG_NAND_IMX_BOOT=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
CONFIG_MTD_NAND_IDS=y
------------------------------------new
CONFIG-------------------------------------
CONFIG_MTD=y
CONFIG_MTD_WRITE=y
CONFIG_MTD_OOB_DEVICE=y
# CONFIG_MTD_RAW_DEVICE is not set
#
# Self contained MTD devices
#
# CONFIG_MTD_DOCG3 is not set
CONFIG_NAND=y
# CONFIG_NAND_ECC_SOFT is not set
CONFIG_NAND_ECC_HW=y
# CONFIG_NAND_ECC_HW_SYNDROME is not set
# CONFIG_NAND_ECC_HW_NONE is not set
CONFIG_NAND_INFO=y
CONFIG_NAND_READ_OOB=y
CONFIG_NAND_BBT=y
CONFIG_NAND_IMX=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
CONFIG_MTD_NAND_IDS=y
Thanks,
Gabriel
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: imx35_nand driver
2012-04-27 10:39 imx35_nand driver Gabriel Tisan
@ 2012-04-27 14:23 ` Sascha Hauer
2012-04-30 12:29 ` Gabriel Tisan
0 siblings, 1 reply; 3+ messages in thread
From: Sascha Hauer @ 2012-04-27 14:23 UTC (permalink / raw)
To: Gabriel Tisan; +Cc: barebox
On Fri, Apr 27, 2012 at 12:39:02PM +0200, Gabriel Tisan wrote:
> 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)?
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.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: imx35_nand driver
2012-04-27 14:23 ` Sascha Hauer
@ 2012-04-30 12:29 ` Gabriel Tisan
0 siblings, 0 replies; 3+ messages in thread
From: Gabriel Tisan @ 2012-04-30 12:29 UTC (permalink / raw)
To: Sascha Hauer; +Cc: barebox
>> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-04-30 12:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-27 10:39 imx35_nand driver Gabriel Tisan
2012-04-27 14:23 ` Sascha Hauer
2012-04-30 12:29 ` Gabriel Tisan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox