Hi Sandeep, To fix the "jffs2_get_inode_nodes: Node header CRC failed at 0x190c6f48" errors, I've been using the "nand markbad" from U-Boot to mark the bad blocks (in the above case, the command would be 'nand markbad 0x190c0000'). Now that I've updated to the latest U-Boot code, Linux now does pick up the bad block tables written from U-Boot (thanks for that!) Once the particular block(s) as bad, I then reflash the NAND partition that was affected and the CRC errors are gone.
However, we're seeing quite a few CRC errors. On one unit, after marking a bunch of bad blocks, then reflashing, we're seeing a few more CRC errors so we have to repeat the process. Again, after the reflash, CRC errors appeared on yet a different address!! Is this common???? We've got an FPGA also on the EMIFA bus (using a different CS). That shouldn't be causing it. If it were, I'm sure we'd be seeing errors on many other units. Any insights? Thanks, Bill -----Original Message----- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Paulraj, Sandeep Sent: Wednesday, March 10, 2010 7:25 AM To: Mile Davidovic; davinci Subject: RE: DM365, NAND and FS > > Hello > On DM365 board I saw following printout: > U-Boot 2009.03 (Nov 16 2009 - 13:02:47) > > I2C: ready > DRAM: 128 MB > NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND > 1GiB 3,3V 8-bit) > Bad block table found at page 524224, version 0x01 > Bad block table found at page 524160, version 0x01 > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V > 8-bit) > Bad block table found at page 524224, version 0x01 > Bad block table found at page 524096, version 0x01 > 2048 MiB > In: serial > .... > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V > 8-bit) > 2 NAND chips detected > Bad block table found at page 524224, version 0x01 > Bad block table found at page 1048512, version 0x01 > Bad block table found at page 524160, version 0x01 > Bad block table found at page 1048384, version 0x01 > nand_read_bbt: Bad block at 0x000000820000 > nand_read_bbt: Bad block at 0x000008aa0000 > nand_read_bbt: Bad block at 0x00000fac0000 > nand_read_bbt: Bad block at 0x000015280000 > nand_read_bbt: Bad block at 0x000016ea0000 > nand_read_bbt: Bad block at 0x00001a720000 > nand_read_bbt: Bad block at 0x00001c120000 > nand_read_bbt: Bad block at 0x0000238e0000 > nand_read_bbt: Bad block at 0x000028340000 > nand_read_bbt: Bad block at 0x000028680000 > nand_read_bbt: Bad block at 0x000030640000 > nand_read_bbt: Bad block at 0x000032560000 > nand_read_bbt: Bad block at 0x0000382c0000 > nand_read_bbt: Bad block at 0x00003bec0000 > nand_read_bbt: Bad block at 0x00003c240000 > nand_read_bbt: Bad block at 0x00004bd60000 > nand_read_bbt: Bad block at 0x00004be40000 > nand_read_bbt: Bad block at 0x0000685c0000 > nand_read_bbt: Bad block at 0x00006ea20000 > nand_read_bbt: Bad block at 0x00006ede0000 > nand_read_bbt: Bad block at 0x00006fda0000 > nand_read_bbt: Bad block at 0x000076020000 > nand_read_bbt: Bad block at 0x00007df40000 > nand_read_bbt: Bad block at 0x00007e720000 > nand_read_bbt: Bad block at 0x00007ffc0000 There is nothing wrong in getting these messages. U-boot is merely reporting bad blocks > Creating 5 MTD partitions on "davinci_nand.0": > 0x000000000000-0x000000f00000 : "bootloader" > 0x000000f00000-0x000001000000 : "params" > 0x000001000000-0x000001400000 : "kernel" > 0x000001400000-0x000021400000 : "filesystem1" > 0x000021400000-0x000080000000 : "filesystem2" > davinci_nand davinci_nand.0: controller rev. 2.3 > ... > mtd->read(0xb8 bytes from 0x190c6f48) returned ECC error > JFFS2 notice: (1007) jffs2_get_inode_nodes: Node header CRC failed at > 0x190c6f48. {0219,c0e0,71000000,99faccda} > JFFS2 notice: (1007) jffs2_get_inode_nodes: Node header CRC failed at > 0x190c6e88. {0219,c0e0,71000000,99faccda} > JFFS2 notice: (1007) jffs2_get_inode_nodes: Node header CRC failed at > 0x190c6d20. {0219,68e0,ac000001,9973d181} > JFFS2 notice: (1007) jffs2_get_inode_nodes: Node header CRC failed at > 0x190c6c60. {0219,c0e0,71000000,99faccda} > JFFS2 notice: (1007) jffs2_get_inode_nodes: Node header CRC failed at > 0x190c6ba0. {0219,c0e0,71000000,99faccda} > ... > Also during boot I got following: > Empty flash at 0x092b9700 ends at 0x092b9800 > Empty flash at 0x460b4d44 ends at 0x460b5000 > Empty flash at 0x59a0d8dc ends at 0x59a0e000 > > My questions are: > - is it normal board behavior (we have issues with JFFS2 and NAND) from > start > - is it possible that we somehow "repair" this board? > - what is "recommended" FS for NAND? > - is any chance that problems with NAND is caused with wrong u-boot, > linux, ... > > Kind regards > mile > _______________________________________________ > Davinci-linux-open-source mailing list > Davinci-linux-open-source@linux.davincidsp.com > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
