• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 784 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

dm6467 NAND bad blocks

Rain Peng
Intellectual 620 points

NAND bad blocks  problem when we enable the ‘NAND Flash device on DaVinci SoC’ in kernel configuration

 

********************************************************

kernel

********************************************************

 

Linux video capture interface: v2.00

i2c /dev entries driver

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2

ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx

MUX: initialized ATAEN

    ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio

hda: TOSHIBA MK4032GAX, ATA DISK drive

ide0 at 0xfec661f0-0xfec661f7,0xfec663f6 on irq 22

No valid DiskOnChip devices found

nand_davinci nand_davinci.0: Using 1-bit hardware ECC

NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit)

Scanning device for bad blocks

Bad eraseblock 0 at 0x00000000

Bad eraseblock 2 at 0x00040000

Bad eraseblock 3 at 0x00060000

Bad eraseblock 4 at 0x00080000

Bad eraseblock 5 at 0x000a0000

Bad eraseblock 6 at 0x000c0000

Bad eraseblock 7 at 0x000e0000

Bad eraseblock 8 at 0x00100000

Bad eraseblock 9 at 0x00120000

......................

......................

Bad eraseblock 1017 at 0x07f20000

Bad eraseblock 1018 at 0x07f40000

Bad eraseblock 1019 at 0x07f60000

Bad eraseblock 1020 at 0x07f80000

Bad eraseblock 1021 at 0x07fa0000

Bad eraseblock 1022 at 0x07fc0000

Bad eraseblock 1023 at 0x07fe0000

Creating 4 MTD partitions on "nand_davinci.0":

0x00000000-0x00080000 : "bootloader"

0x00080000-0x000a0000 : "params"

0x000a0000-0x004a0000 : "kernel"

0x004a0000-0x08000000 : "filesystem"

nand_davinci nand_davinci.0: hardware revision: 2.2

Initializing USB Mass Storage driver...

 

********************************************************

do you know what's the problem?

  • 0
    Prodigy 40 points

    I have the same problem with the 6467, I have not been able to find the solution so far.

     

  • 0
    TI__Mastermind 37340 points

    these bad block messages are normal.  As part of the working system, NAND bad block list is kept in a special section of memory and listed as the system boots to make you aware of where those bad blocks are so that the user avoids using them.  I suppose with some mods to driver, these messages could be suppressed.  FYI, all NAND parts normally come with a set of bad blocks from the manufacturer.

  • 0 in reply to Juan Gonzales
    Intellectual 620 points

    thank you

    I got some progress.I use the UBL built from PSP_02_00_00_140 via CCS and the same uboot.bin,those problems go away.

    But if I use the uboot.bin built from PSP_02_00_00_140 ,a new problem occurs,

    Booting PSP Boot Loader

    Starting NAND Copy

    Booting Application @ 0x81080000


    U-Boot 1.2.0 (Jan  1 2010 - 13:11:22)

    I2C:   ready
    DRAM:  256 MB
    unknown vendor=0 Flash:  0 kB
    NAND:  NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit)
    No oob scheme defined for oobsize 256
    BUG: failure at nand_base.c:3398/nand_scan()!
    BUG!

    what's the problem of No oob scheme defined for oobsize 256 ?

  • 0 in reply to Rain Peng
    TI__Expert 4510 points

    I am assuming you are using Rev H of DM6467 EVM board.

    The issue is due to a bug in the core NAND driver in u-boot, while reading the extended id for calculating oob size, it includes a part of 'minimum sequential access time' in the calculation.

    The RevH boards use the same NAND part as  previous EVMs, but use an updated version of the chip. The issue was being masked on earlier revisions due to erroneous part being read was 0.

    Make the following change in uboot under drivers/nand/nand_base.c

    Change line 3255 from

       mtd->oobsize = (8 << (extid & 0x03)) * (mtd->oobblock / 512);

    to

       mtd->oobsize = (8 << (extid & 0x01)) * (mtd->oobblock / 512);

    Recompile the uboot and flash this version..