mx31pdk: Add NAND support
Subsystems (2)
PATCH 1/1 mx31pdk: Add NAND support
Add NAND support to MX31PDK board.
--- arch/arm/mach-mx3/mach-mx31_3ds.c | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
arch/arm/mach-mx3/mach-mx31_3ds.c +7 -0
@@ -34,6 +34,7 @@#include <mach/board-mx31pdk.h> #include <mach/imx-uart.h> #include <mach/iomux-mx3.h> +#include <mach/mxc_nand.h> #include "devices.h" /*!
@@ -80,6 +81,11 @@ static struct resource smsc911x_resources[] = { }, }; +static struct mxc_nand_platform_data mx31pdk_nand_board_info = { + .width =1 , + .hw_ecc =1 , +}; +static struct platform_device smsc911x_device = { .name ="smsc911x" , .id =-1 ,
@@ -236,6 +242,7 @@ static void __init mxc_board_init(void) "mx31pdk");mxc_register_device (&mxc_uart_device0, &uart_pdata); +mxc_register_device (&mxc_nand_device, &mx31pdk_nand_board_info);if (!mx31pdk_init_expio ())platform_device_register (&smsc911x_device);
Signature · 1 line
1.6.0.4
PATCH 1/1 mx31pdk: Add NAND support
Quoted 3 lines · Fabio Estevam
Add NAND support to MX31PDK board.
Signed-off-by Fabio Estevam <[email protected]>
Mmm.. maybe I waited too much before pull my work on this board.. Fabio, don't you think to change the namespace in mach-mx31_3ds to accomplish to the new machine file name before adding some more functionality?
I am waiting for the rebase of mxc-master on 2.6.34-rc1 (or linux-next).
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Hi Alberto,
Quoted 12 lines · Alberto Panizzo
From: Alberto Panizzo <[email protected]>
Subject: Re: [PATCH] mx31pdk: Add NAND support
To: "Fabio Estevam" <[email protected]>
Cc: s.hauer at pengutronix.de, linux-arm-kernel at lists.infradead.org
Date: Thursday, February 25, 2010, 8:58 AMQuoted 3 lines · Fabio Estevam
Add NAND support to MX31PDK board.
Signed-off-by Fabio Estevam <[email protected]>
Quoted 7 lines
Mmm.. maybe I waited too much before pull my work on this board..
Fabio, don't you think to change the namespace in mach-mx31_3ds
to accomplish to the new machine file name before adding some more
functionality?
I am not a big fan of the mach-mx31_3ds name. I know that this comes from the MACH name, but the name we use these days is MX31PDK as it is advertised on Freescale's website (www.freescale.com/imx31pdk).
Should we really rename all mx31pdk references inside mach-mx31_3ds.c ?
U-boot also references this board as mx31pdk.
MX35PDK board seems not to follow the same logic:
MACH name is MX35_3DS and board name is mach-mx35pdk.c
I prefer the MX35 approach.
Regards,
Fabio Estevam
PATCH 1/1 mx31pdk: Add NAND support
Hello,
Quoted 1 line
MACH name is
MX35_3DSand board name ismach-mx35pdk.c
Oh, I must have missed that when massrenaming the machine files. (commit 321ed164). Sorry :-)
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
PATCH 1/1 mx31pdk: Add NAND support
Quoted 9 lines · Uwe Kleine-K?nig
Hello,
Quoted 1 line
MACH name is
MX35_3DSand board name ismach-mx35pdk.cOh, I must have missed that when massrenaming the machine files. (commit
321ed164). Sorry :-)Best regards
Uwe
Uwe, so what is the next step? we can re-rename the machine file to mach-mx31pdk.c?
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Hello,
Quoted 10 lines
Quoted 7 lines
Quoted 1 line
MACH name is
MX35_3DSand board name ismach-mx35pdk.cOh, I must have missed that when massrenaming the machine files. (commit
321ed164). Sorry :-)Best regards
UweUwe, so what is the next step? we can re-rename the machine file to
mach-mx31pdk.c?
I suggest to do
mv mach-mx35pdk.c mach-mx35_3ds.c
to make it consistant.
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
PATCH 1/1 mx31pdk: Add NAND support
Quoted 12 lines · Uwe Kleine-K?nig
Hello,
Quoted 10 lines
Quoted 7 lines
Quoted 1 line
MACH name is
MX35_3DSand board name ismach-mx35pdk.cOh, I must have missed that when massrenaming the machine files. (commit
321ed164). Sorry :-)Best regards
UweUwe, so what is the next step? we can re-rename the machine file to
mach-mx31pdk.c?
Quoted 9 lines
I suggest to do
mv mach-mx35pdk.c mach-mx35_3ds.cto make it consistant.
Best regards
Uwe
:) consistant with the MACH name, but the market and freescale call these mx[N]pdk, I don't know who registered those names but Fabio addressed a not obvious problem.
For me it is not a problem and I think that the motivations are: Freescale can build different type of Product Development Kit, indeed the 3-Stack is the particular one -> call it mx[N]_3ds.c
But Freescale do not produce multiple mx[N] PDKs.
Best regards
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
2010/2/26 Alberto Panizzo <[email protected]> [...]
Quoted 5 lines
For me it is not a problem and I think that the motivations are: Freescale can build different type of Product Development Kit, indeed the 3-Stack is the particular one -> call it mx[N]_3ds.c
But Freescale do not produce multiple mx[N] PDKs.
Yes it does: i.MX25 PDK, MX27 PDK, MX31 PDK and the MX35 PDK.
Basically, everything which Freescale used to call a "i.MX[N] 3-Stack Development System", Freescale now refers to as "i.MX[N] PDK" (Platform Development Kit).
Best regards,
Ivo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100226/26a11b34/attachment-0001.htm>
PATCH 1/1 mx31pdk: Add NAND support
In reply to Fabio EstevamHi Fabio,
Quoted 20 lines · Fabio Estevam
Add NAND support to MX31PDK board.
Signed-off-by Fabio Estevam <[email protected]>--- arch/arm/mach-mx3/mach-mx31_3ds.c | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)arch/arm/mach-mx3/mach-mx31_3ds.c +1
-0@@ -34,6 +34,7 @@#include <mach/board-mx31pdk.h> #include <mach/imx-uart.h> #include <mach/iomux-mx3.h> +#include <mach/mxc_nand.h> #include "devices.h" /*!
arch/arm/mach-mx3/mach-mx31_3ds.c static struct resource smsc911x_resources[] = { · line 88
Quoted 8 lines
arch/arm/mach-mx3/mach-mx31_3ds.c +5
-0@@ -80,6 +81,11 @@ static struct resource smsc911x_resources[] = { }, }; +static struct mxc_nand_platform_data mx31pdk_nand_board_info = { + .width =1 , + .hw_ecc =1 , +}; +
Are you sure that this works? Don't you see a lot of Bad blocks reports in boot messages?
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Hi Alberto,
Quoted 37 lines · Alberto Panizzo
From: Alberto Panizzo <[email protected]>
Subject: Re: [PATCH] mx31pdk: Add NAND support
To: "Fabio Estevam" <[email protected]>
Cc: linux-arm-kernel at lists.infradead.org, s.hauer at pengutronix.de
Date: Thursday, February 25, 2010, 9:12 AM
Hi Fabio,Quoted 5 lines · Fabio Estevam
Add NAND support to MX31PDK board.
Signed-off-by Fabio Estevam <[email protected]>---
?arch/arm/mach-mx3/mach-mx31_3ds.c|? ?7 +++++++
Quoted 1 line
? 1 files changed, 7 insertions(+), 0
deletions(-)
Review
Quoted 2 lines
(quoted diff) +0
-0
b/arch/arm/mach-mx3/mach-mx31_3ds.carch/arm/mach-mx3/mach-mx31_3ds.c static struct resource
Quoted 12 lines
index b88c18a..2d78754 100644
arch/arm/mach-mx3/mach-mx31_3ds.c +0
-0@@ -34,6 +34,7 @@? #include <
mach/board-mx31pdk.h>
? #include <mach/imx-uart.h>
? #include <mach/iomux-mx3.h>
+#include <mach/mxc_nand.h>
? #include "devices.h"
?
? /*!arch/arm/mach-mx3/mach-mx31_3ds.c +0
-0@@ -80,6 +81,11 @@ static struct resourcesmsc911x_resources[] = {
Quoted 4 lines
arch/arm/mach-mx3/mach-mx31_3ds.c +0
-0? ??? }, ? };?
+static structmxc_nand_platform_data
mx31pdk_nand_board_info= {
Quoted 8 lines
arch/arm/mach-mx3/mach-mx31_3ds.c static struct resource smsc911x_resources[] = { · line 88
Quoted 4 lines
+??? .width = 1,
+??? .hw_ecc = 1,arch/arm/mach-mx3/mach-mx31_3ds.c +2
-0+}; +Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?
I followed the same approach used on other i.MX boards. This is what I see:
...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xaa (Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at 0x000000540000
Bad eraseblock 125 at 0x000000fa0000
Bad eraseblock 887 at 0x000006ee0000
Bad eraseblock 1750 at 0x00000dac0000
Bad eraseblock 2046 at 0x00000ffc0000
Bad eraseblock 2047 at 0x00000ffe0000
Registering mxc_nand as whole device
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = {
.width = 1,
.hw_ecc = 1,
.flash_bbt =1,
};The bad block messages go away.
What would be the correct way?
Thanks,
Fabio Estevam
PATCH 1/1 mx31pdk: Add NAND support
Hi Fabio,
Quoted 70 lines · Fabio Estevam
Hi Alberto,
Quoted 37 lines · Alberto Panizzo
From: Alberto Panizzo <[email protected]>
Subject: Re: [PATCH] mx31pdk: Add NAND support
To: "Fabio Estevam" <[email protected]>
Cc: linux-arm-kernel at lists.infradead.org, s.hauer at pengutronix.de
Date: Thursday, February 25, 2010, 9:12 AM
Hi Fabio,Quoted 5 lines · Fabio Estevam
Add NAND support to MX31PDK board.
Signed-off-by Fabio Estevam <[email protected]>---
arch/arm/mach-mx3/mach-mx31_3ds.c|7 +++++++
Quoted 1 line
1 files changed, 7 insertions(+), 0deletions(-)
Review
Quoted 2 lines
(quoted diff) +0
-0
b/arch/arm/mach-mx3/mach-mx31_3ds.carch/arm/mach-mx3/mach-mx31_3ds.c static struct resource
Quoted 12 lines
index b88c18a..2d78754 100644
arch/arm/mach-mx3/mach-mx31_3ds.c +1
-0@@ -34,6 +34,7 @@#include <mach/board-mx31pdk.h> #include <mach/imx-uart.h> #include <mach/iomux-mx3.h> +#include <mach/mxc_nand.h> #include "devices.h" /*! @@ -80,6 +81,11 @@ static struct resourcesmsc911x_resources[] = {
arch/arm/mach-mx3/mach-mx31_3ds.c static struct resource · line 84
Quoted 4 lines
arch/arm/mach-mx3/mach-mx31_3ds.c +1
-0}, }; +static struct mxc_nand_platform_data
mx31pdk_nand_board_info= {Quoted 8 lines
arch/arm/mach-mx3/mach-mx31_3ds.c static struct resource smsc911x_resources[] = { · line 88
Quoted 4 lines
arch/arm/mach-mx3/mach-mx31_3ds.c +4
-0+ .width = 1, + .hw_ecc = 1, +}; +Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I see:
...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole deviceIf I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };
Quoted 7 lines
The bad block messages go away.
What would be the correct way?
Thanks,
Fabio Estevam
Well, I am not very experienced on mtd devices, but if you trust what your bootloader say, Bad blocks reporting must not change. On my mx31_3ds board, omitting that row means A LOT of bad block reporting that is in contrast with the bootloader.
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
In reply to Fabio EstevamQuoted 16 lines · Fabio Estevam
Quoted 3 lines
Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I see:
...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole device
Quoted 7 lines
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };
Your bootloader also use a Bad Block Table? Then also your kernel should use it. If hardware ECC is in use, its always a good idea to collect the bad blocks into a BBT. Most of the time you can't control at which offset in the OOB data the NAND controller will store the ECC sum. There is the risk it will destroy manufacturer's bad block markers. So, its better to collect these marked bad blocks into a BBT the first time you use the NAND device. After that _only_ the BBT should be used to handle bad blocks (in the boot loader and the kernel).
jbe
Signature · 4 lines
Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
PATCH 1/1 mx31pdk: Add NAND support
Quoted 34 lines · Juergen Beisert
Quoted 16 lines · Fabio Estevam
Quoted 3 lines
Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I see:
...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole deviceQuoted 7 lines
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };Your bootloader also use a Bad Block Table? Then also your kernel should use it. If hardware ECC is in use, its always a good idea to collect the bad blocks into a BBT. Most of the time you can't control at which offset in the OOB data the NAND controller will store the ECC sum. There is the risk it will destroy manufacturer's bad block markers. So, its better to collect these marked bad blocks into a BBT the first time you use the NAND device. After that _only_ the BBT should be used to handle bad blocks (in the boot loader and the kernel).
Quoted 2 lines
jbe
Thank you Juergen to participate on this thread.
Ok, so with this board shall be enabled the flash_bbt checking because the bootloader uses it. But how do you explain that on Mine board the kernel recognize it correctly and in Fabio's board the kernel prompt disagree with the bootloader one? It is a kind of bootloader issue?
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Hi Alberto,
Quoted 35 lines · Alberto Panizzo
Quoted 25 lines · Juergen Beisert
Quoted 16 lines · Fabio Estevam
Quoted 3 lines
Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I
see: ...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole deviceQuoted 7 lines
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };Quoted 8 lines
Your bootloader also use a Bad Block Table? Then also your kernel should use it. If hardware ECC is in use, its always a good idea to collect the bad blocks into a BBT. Most of the time you can't control at which offset in the OOB data the NAND controller will store the ECC sum. There is the risk it will destroy manufacturer's bad block markers. So, its better to collect these marked bad blocks into a BBT the first time you use the NAND device. After that _only_ the BBT should be used to handle bad blocks (in the boot loader and the kernel).
Quoted 5 lines
Thank you Juergen to participate on this thread.
Ok, so with this board shall be enabled theflash_bbtchecking because the bootloader uses it. But how do you explain that on Mine board the kernel recognize it correctly and in Fabio's board the kernel prompt disagree with the bootloader one? It is a kind of bootloader issue?
Here on my i.MX35 based system the bootloader reports:
NAND device: Manufacturer ID: 0x20, Chip ID: 0xac (ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01nand_read_bbt: Bad block at 0x01d00000nand_read_bbt: Bad block at 0x10020000nand_read_bbt: Bad block at 0x10040000nand_read_bbt: Bad block at 0x10060000nand_read_bbt: Bad block at 0x10080000nand_read_bbt: Bad block at 0x100a0000nand_read_bbt: Bad block at 0x100e0000nand_read_bbt: Bad block at 0x10120000nand_read_bbt: Bad block at 0x10160000nand_read_bbt: Bad block at 0x101a0000nand_read_bbt: Bad block at 0x101c0000nand_read_bbt: Bad block at 0x10200000nand_read_bbt: Bad block at 0x10240000
And the starting kernel reports:
[...]
NAND device: Manufacturer ID: 0x20, Chip ID: 0xac (ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01nand_read_bbt: Bad block at 0x000001d00000nand_read_bbt: Bad block at 0x000010020000nand_read_bbt: Bad block at 0x000010040000nand_read_bbt: Bad block at 0x000010060000nand_read_bbt: Bad block at 0x000010080000nand_read_bbt: Bad block at 0x0000100a0000nand_read_bbt: Bad block at 0x0000100e0000nand_read_bbt: Bad block at 0x000010120000nand_read_bbt: Bad block at 0x000010160000nand_read_bbt: Bad block at 0x0000101a0000nand_read_bbt: Bad block at 0x0000101c0000nand_read_bbt: Bad block at 0x000010200000nand_read_bbt: Bad block at 0x000010240000
[...]
Both are configured to use a BBT and will handle the bad blocks in the same manner.
Regards,
Juergen
Signature · 4 lines
Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
PATCH 1/1 mx31pdk: Add NAND support
Quoted 84 lines · Juergen Beisert
Hi Alberto,
Quoted 35 lines · Alberto Panizzo
Quoted 25 lines · Juergen Beisert
Quoted 16 lines · Fabio Estevam
Quoted 3 lines
Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I
see: ...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole deviceQuoted 7 lines
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };Quoted 8 lines
Your bootloader also use a Bad Block Table? Then also your kernel should use it. If hardware ECC is in use, its always a good idea to collect the bad blocks into a BBT. Most of the time you can't control at which offset in the OOB data the NAND controller will store the ECC sum. There is the risk it will destroy manufacturer's bad block markers. So, its better to collect these marked bad blocks into a BBT the first time you use the NAND device. After that _only_ the BBT should be used to handle bad blocks (in the boot loader and the kernel).
Quoted 5 lines
Thank you Juergen to participate on this thread.
Ok, so with this board shall be enabled theflash_bbtchecking because the bootloader uses it. But how do you explain that on Mine board the kernel recognize it correctly and in Fabio's board the kernel prompt disagree with the bootloader one? It is a kind of bootloader issue?Here on my i.MX35 based system the bootloader reports:
NAND device: Manufacturer ID:
0x20, Chip ID:0xac(ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version0x01
Bad block table found at page 262016, version0x01nand_read_bbt: Bad block at0x01d00000nand_read_bbt: Bad block at0x10020000nand_read_bbt: Bad block at0x10040000nand_read_bbt: Bad block at0x10060000nand_read_bbt: Bad block at0x10080000nand_read_bbt: Bad block at0x100a0000nand_read_bbt: Bad block at0x100e0000nand_read_bbt: Bad block at0x10120000nand_read_bbt: Bad block at0x10160000nand_read_bbt: Bad block at0x101a0000nand_read_bbt: Bad block at0x101c0000nand_read_bbt: Bad block at0x10200000nand_read_bbt: Bad block at0x10240000And the starting kernel reports:
[...]
NAND device: Manufacturer ID:0x20, Chip ID:0xac(ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version0x01
Bad block table found at page 262016, version0x01nand_read_bbt: Bad block at0x000001d00000nand_read_bbt: Bad block at0x000010020000nand_read_bbt: Bad block at0x000010040000nand_read_bbt: Bad block at0x000010060000nand_read_bbt: Bad block at0x000010080000nand_read_bbt: Bad block at0x0000100a0000nand_read_bbt: Bad block at0x0000100e0000nand_read_bbt: Bad block at0x000010120000nand_read_bbt: Bad block at0x000010160000nand_read_bbt: Bad block at0x0000101a0000nand_read_bbt: Bad block at0x0000101c0000nand_read_bbt: Bad block at0x000010200000nand_read_bbt: Bad block at0x000010240000
[...]
Quoted 6 lines
Both are configured to use a BBT and will handle the bad blocks in the same manner.
Regards,
Juergen
Well, also for me. With Bbt active:
++Searching for BBT table in the flash ...
.
Found version 1 Bbt0 at block 2047 (0xffe0000) Block 55 is bad
Block 1688 is bad
Block 1735 is bad
Block 1742 is bad
Total bad blocks: 4
... Read from 0x07ee0000-0x07f00000 at 0x00080000: .. ... Read from 0x07ed3000-0x07ed4000 at 0x0009f000: . PMIC ID: 0x0000009b [Rev: 3.3]
...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xaa (Samsung NAND 256MiB 1,8V 8-b) Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01nand_read_bbt: Bad block at 0x0000006e0000nand_read_bbt: Bad block at 0x00000d300000nand_read_bbt: Bad block at 0x00000d8e0000nand_read_bbt: Bad block at 0x00000d9c0000
That considering a block size of 64 pages, it is consistent.
But without bad block table enabled:
NAND device: Manufacturer ID: 0xec, Chip ID: 0xaa (Samsung NAND 256MiB 1,8V 8-b) Scanning device for bad blocks
Bad eraseblock 4 at 0x000000080000
Bad eraseblock 8 at 0x000000100000
Bad eraseblock 9 at 0x000000120000
Bad eraseblock 10 at 0x000000140000
Bad eraseblock 11 at 0x000000160000
Bad eraseblock 12 at 0x000000180000
all blocks..
Bad eraseblock 342 at 0x000002ac0000
Bad eraseblock 1688 at 0x00000d300000
Bad eraseblock 1735 at 0x00000d8e0000
Bad eraseblock 1742 at 0x00000d9c0000
Bad eraseblock 2046 at 0x00000ffc0000
Bad eraseblock 2047 at 0x00000ffe0000
All blocks went bad.
I had seen this behaviour developing the machine support for the Armadillo500 board, and that was solved by updating the ecc layout management due to bad 2K page sized NAND flash support. With the new version (V2) of the driver this comes back..
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Quoted 136 lines · Alberto Panizzo
Quoted 85 lines · Juergen Beisert
Hi Alberto,
Quoted 36 lines · Alberto Panizzo
Quoted 25 lines · Juergen Beisert
Quoted 16 lines · Fabio Estevam
Quoted 3 lines
Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?I followed the same approach used on other i.MX boards. This is what I see: ...
NAND device: Manufacturer ID:0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-bit) Scanning device for bad blocks
Bad eraseblock 42 at0x000000540000
Bad eraseblock 125 at0x000000fa0000
Bad eraseblock 887 at0x000006ee0000
Bad eraseblock 1750 at0x00000dac0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Registeringmxc_nandas whole deviceQuoted 7 lines
If I define it as:
static struct mxc_nand_platform_data mx31pdk_nand_board_info = { .width = 1, .hw_ecc = 1, .flash_bbt =1, };Quoted 9 lines
Your bootloader also use a Bad Block Table? Then also your kernel should use it. If hardware ECC is in use, its always a good idea to collect the bad blocks into a BBT. Most of the time you can't control at which offset in the OOB data the NAND controller will store the ECC sum. There is the risk it will destroy manufacturer's bad block markers. So, its better to collect these marked bad blocks into a BBT the first time you use the NAND device. After that _only_ the BBT should be used to handle bad blocks (in the boot loader and the kernel).
Quoted 5 lines
Thank you Juergen to participate on this thread.
Ok, so with this board shall be enabled theflash_bbtchecking because the bootloader uses it. But how do you explain that on Mine board the kernel recognize it correctly and in Fabio's board the kernel prompt disagree with the bootloader one? It is a kind of bootloader issue?Here on my i.MX35 based system the bootloader reports:
NAND device: Manufacturer ID:
0x20, Chip ID:0xac(ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version0x01Bad block table found at page 262016, version0x01nand_read_bbt: Bad block at0x01d00000nand_read_bbt: Bad block at0x10020000nand_read_bbt: Bad block at0x10040000nand_read_bbt: Bad block at0x10060000nand_read_bbt: Bad block at0x10080000nand_read_bbt: Bad block at0x100a0000nand_read_bbt: Bad block at0x100e0000nand_read_bbt: Bad block at0x10120000nand_read_bbt: Bad block at0x10160000nand_read_bbt: Bad block at0x101a0000nand_read_bbt: Bad block at0x101c0000nand_read_bbt: Bad block at0x10200000nand_read_bbt: Bad block at0x10240000And the starting kernel reports:
[...]
NAND device: Manufacturer ID:0x20, Chip ID:0xac(ST Micro NAND 512MiB 1,8V 8-bit) Bad block table found at page 262080, version0x01Bad block table found at page 262016, version0x01nand_read_bbt: Bad block at0x000001d00000nand_read_bbt: Bad block at0x000010020000nand_read_bbt: Bad block at0x000010040000nand_read_bbt: Bad block at0x000010060000nand_read_bbt: Bad block at0x000010080000nand_read_bbt: Bad block at0x0000100a0000nand_read_bbt: Bad block at0x0000100e0000nand_read_bbt: Bad block at0x000010120000nand_read_bbt: Bad block at0x000010160000nand_read_bbt: Bad block at0x0000101a0000nand_read_bbt: Bad block at0x0000101c0000nand_read_bbt: Bad block at0x000010200000nand_read_bbt: Bad block at0x000010240000
[...]Quoted 5 lines
Both are configured to use a BBT and will handle the bad blocks in the same manner.
Regards,
JuergenWell, also for me. With Bbt active:
++Searching for BBT table in the flash ...
.
Found version 1 Bbt0 at block 2047 (0xffe0000) Block 55 is bad
Block 1688 is bad
Block 1735 is bad
Block 1742 is bad
Total bad blocks: 4
... Read from 0x07ee0000-0x07f00000 at0x00080000: .. ... Read from 0x07ed3000-0x07ed4000 at0x0009f000: . PMIC ID:0x0000009b[Rev: 3.3]...
NAND device: Manufacturer ID:
0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-b) Bad block table found at page 131008, version0x01
Bad block table found at page 130944, version0x01nand_read_bbt: Bad block at0x0000006e0000nand_read_bbt: Bad block at0x00000d300000nand_read_bbt: Bad block at0x00000d8e0000nand_read_bbt: Bad block at0x00000d9c0000That considering a block size of 64 pages, it is consistent.
But without bad block table enabled:
NAND device: Manufacturer ID:
0xec, Chip ID:0xaa(Samsung NAND 256MiB 1,8V 8-b) Scanning device for bad blocks
Bad eraseblock 4 at0x000000080000
Bad eraseblock 8 at0x000000100000
Bad eraseblock 9 at0x000000120000
Bad eraseblock 10 at0x000000140000
Bad eraseblock 11 at0x000000160000
Bad eraseblock 12 at0x000000180000
all blocks..
Bad eraseblock 342 at0x000002ac0000
Bad eraseblock 1688 at0x00000d300000
Bad eraseblock 1735 at0x00000d8e0000
Bad eraseblock 1742 at0x00000d9c0000
Bad eraseblock 2046 at0x00000ffc0000
Bad eraseblock 2047 at0x00000ffe0000
Quoted 5 lines
All blocks went bad.
I had seen this behaviour developing the machine support for the Armadillo500 board, and that was solved by updating the ecc layout management due to bad 2K page sized NAND flash support. With the new version (V2) of the driver this comes back..
Maybe you previously used a driver that does not report the byte at offset 5 in the OOB as used (for 512 byte page size). So this byte was used (maybe) by jffs2 for example. When you switch off the BBT now, all these blocks seems marked as bad, because then byte 5 will be used again. For 2k page size, the bad block information is stored in byte 0 and 1 in the OOB. And maybe the same happend to these bytes by an old driver.
Regards,
Juergen
Signature · 4 lines
Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
PATCH 1/1 mx31pdk: Add NAND support
In reply to Fabio EstevamHi Sascha,
Quoted 54 lines · Fabio Estevam
From: Fabio Estevam <[email protected]>
Subject: [PATCH] mx31pdk: Add NAND support
To: linux-arm-kernel at lists.infradead.org
Cc: s.hauer at pengutronix.de
Date: Wednesday, February 24, 2010, 10:58 PM Add NAND support to MX31PDK board.Signed-off-by Fabio Estevam <[email protected]>---
arch/arm/mach-mx3/mach-mx31_3ds.c|? ? 7
+++++++1 files changed, 7 insertions(+), 0 deletions(-)arch/arm/mach-mx3/mach-mx31_3ds.c +6
-0@@ -34,6 +34,7 @@#include <mach/board-mx31pdk.h> #include <mach/imx-uart.h> #include <mach/iomux-mx3.h> +#include <mach/mxc_nand.h> #include "devices.h" /*! @@ -80,6 +81,11 @@ static struct resource smsc911x_resources[] = { ??? }, }; +static struct mxc_nand_platform_data mx31pdk_nand_board_info = { +??? .width = 1, +??? .hw_ecc = 1, +}; +static struct platform_device smsc911x_device = {??? .name???
??? = "smsc911x",
??? .id???
??? = -1,arch/arm/mach-mx3/mach-mx31_3ds.c +0
-0@@ -236,6 +242,7 @@ static void __initmxc_board_init (void) ??? ??? ??? ??? ? ? ? "mx31pdk"); ??? mxc_register_device(&mxc_uart_device0,
&uart_pdata);
+???mxc_register_device(&mxc_nand_device, &mx31pdk_nand_board_info);
Quoted 5 lines
??? if (!mx31pdk_init_expio())
??? ???platform_device_register(&smsc911x_device);Signature · 1 line
1.6.0.4
Do you think this patch is OK?
Regards,
Fabio Estevam
PATCH 1/1 mx31pdk: Add NAND support
Dear Fabio,
Quoted 2 lines · Fabio Estevam
Hi Sascha,
...
Quoted 6 lines
Do you think this patch is OK?
Regards,
Fabio Estevam
I do not know if Sascha own an i.MX31 PDK board and I do not know how Sascha could say if your patch is correct or not until WE (i.MX31 PDK owners) are in disagree on this code. So _please_, be _kind_ and continue the debugging of this code.
(Why your bootloader correctly read the BBT and the driver not?)
Another thing: I am a new graduated developer, I do this work keeping in mind my future and until now I am not paid to do this. What I gain is in experience and resume with my name in the kernel Git log.
If you are thinking to push my entire work with your name only because I sent you my own mx31_3ds.c out of this mailing list you are in _wrong_.
Review of my work are welcome, BUT please, do not overcome me thinking that Sascha can merely arbitrate between us.
Best regards,
Signature · 4 lines
Alberto
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
Hi Alberto,
Quoted 16 lines · Alberto Panizzo
From: Alberto Panizzo <[email protected]>
Subject: Re: [PATCH] mx31pdk: Add NAND support
To: "Fabio Estevam" <[email protected]>
Cc: linux-arm-kernel at lists.infradead.org, s.hauer at pengutronix.de
Date: Saturday, February 27, 2010, 12:25 PM
Dear Fabio,Quoted 2 lines · Fabio Estevam
Hi Sascha,
...
Quoted 5 lines
Do you think this patch is OK?
Regards,
Quoted 8 lines
Quoted 1 line
Fabio Estevam
I do not know if Sascha own an i.MX31 PDK board and I do not know how Sascha could say if your patch is correct or not
until WE (i.MX31 PDK owners) are in disagree on this code. So _please_, be _kind_ and continue the debugging of this code.
Ok, I just did what all the others i.MX boards did.
Quoted 10 lines
(Why your bootloader correctly read the BBT and the driver not?)
Another thing: I am a new graduated developer, I do this work
keeping in mind my future and until now I am not paid to do this.
What I gain is in experience and resume with my name in thekernel Git log.
This is great. Please continue with this work.
Quoted 5 lines
If you are thinking to push my entire work with your name only
because I sent you my ownmx31_3ds.cout of this mailing list
you are in _wrong_.
This is not my intention. The mx31_3ds.c you sent me helped me to solve a different issue related to the LCD driver. The NAND patch I submitted in this list is not the same you had in your code as I did not pass flash_bbt. So your comment that I am pushing your entire work is not fair.
Quoted 4 lines
Review of my work are welcome, BUT please, do not overcome me
thinking that Sascha can merely arbitrate between us.
Again, Alberto, I would love to work together with you and make i.MX support better.
Regards,
Fabio Estevam
PATCH 1/1 mx31pdk: Add NAND support
Quoted 58 lines · Fabio Estevam
Hi Alberto,
Quoted 16 lines · Alberto Panizzo
From: Alberto Panizzo <[email protected]>
Subject: Re: [PATCH] mx31pdk: Add NAND support
To: "Fabio Estevam" <[email protected]>
Cc: linux-arm-kernel at lists.infradead.org, s.hauer at pengutronix.de
Date: Saturday, February 27, 2010, 12:25 PM
Dear Fabio,Quoted 2 lines · Fabio Estevam
Hi Sascha,
...
Quoted 5 lines
Do you think this patch is OK?
Regards,
Quoted 8 lines
Quoted 1 line
Fabio Estevam
I do not know if Sascha own an i.MX31 PDK board and I do not know how Sascha could say if your patch is correct or not
until WE (i.MX31 PDK owners) are in disagree on this code. So _please_, be _kind_ and continue the debugging of this code.Ok, I just did what all the others i.MX boards did.
Quoted 10 lines
(Why your bootloader correctly read the BBT and the driver not?)
Another thing: I am a new graduated developer, I do this work
keeping in mind my future and until now I am not paid to do this.
What I gain is in experience and resume with my name in thekernel Git log.
This is great. Please continue with this work.
Quoted 5 lines
If you are thinking to push my entire work with your name only
because I sent you my ownmx31_3ds.cout of this mailing list
you are in _wrong_.This is not my intention. The
mx31_3ds.cyou sent me helped me to solve a different issue related to the LCD driver. The NAND patch I submitted in this list is not the same you had in your code as I did not passflash_bbt. So your comment that I am pushing your entire work is not fair.Quoted 4 lines
Review of my work are welcome, BUT please, do not overcome me
thinking that Sascha can merely arbitrate between us.
Quoted 6 lines
Again, Alberto, I would love to work together with you and make i.MX support better.
Regards,
Fabio Estevam
Ok Fabio, nevermind.. I trust the pure intentions of the kernel community and yours. For one moment I've lost the compass (we say this in Italy, I don't know if it is valid too here) and I apologize for unfairness (I've spent months on this board! urk!)
Returning on the subject, I was not the first owner of the i.MX pdk board in my possess, and since the freescale NAND driver uses a private OOB schema, others could have soiled my nand chip overwriting the Bad block bits in the OOB.
The things are two:
1- I have to clean my NAND chip. -> the bad block scanning could
get rid of true Bad blocks.
2- Why the mxc_nand driver do not read your bbt as the
bootloader do?
What version of redboot are you using?
I am Very curious on this disagreement..!
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)