mx31pdk: Add NAND support
PATCH 1/1 mx31pdk: Add NAND support
--- On Thu, 2/25/10, Fabio Estevam <[email protected]> wrote:
...
Quoted 6 lines
Quoted 2 lines
Are you sure that this works? Don't you see a lot of
Bad
Quoted 2 lines
blocks reports
in boot messages?
Quoted 13 lines
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? ? ?
? ? ? ? ? ? ? ?
Just looked at what Redboot reported:
++Searching for BBT table in the flash ...
.
Found version 1 Bbt0 at block 2047 (0xffe0000)
Block 42 is bad
Block 125 is bad
Block 887 is bad
Block 1750 is bad
Total bad blocks: 4
So the only mismatch is 2046 eraseblock.
Regards,
Fabio Estevam
PATCH 1/1 mx31pdk: Add NAND support
Quoted 35 lines · Fabio Estevam
--- On Thu, 2/25/10, Fabio Estevam <[email protected]> wrote:
...
Quoted 6 lines
Quoted 2 lines
Are you sure that this works? Don't you see a lot of
Bad
Quoted 2 lines
blocks reports
in boot messages?Quoted 13 lines
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 at0x00000ffe0000Just looked at what Redboot reported:
++Searching for BBT table in the flash ...
.
Found version 1 Bbt0 at block 2047 (0xffe0000)
Block 42 is bad
Block 125 is bad
Block 887 is bad
Block 1750 is bad
Total bad blocks: 4
Quoted 6 lines
So the only mismatch is 2046 eraseblock.
Regards,
Fabio Estevam
What kernel are you running? In particular, what version of mxc_nand.c are you building?
Recently the mxc_nand.c has been updated to support newer i.MX SoC and the problem come after this update. (add NFC_NAND V2 support)
Signature · 4 lines
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)PATCH 1/1 mx31pdk: Add NAND support
--- On Thu, 2/25/10, Alberto Panizzo <[email protected]>
...
Quoted 6 lines
What kernel are you running? In particular, what version of
mxc_nand.care you building?
Recently themxc_nand.chas been updated to support newer i.MX SoC
and the problem come after this update. (addNFC_NANDV2 support)
Running latest kernel from mxc-master.
Regards,
Fabio Estevam