• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 102 subscribers
  • Views 575 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.

NAND write issue is DM355

Thalib
Intellectual 580 points

Hi,

In our custom board we are using DM355 with 64MB nand from ST,

Now the uboot is up and running we. Our board has only NAND flash storage. ubl and uboot are in NAND

 

we tried to erase/ write nand offset between 0x40000 to 0x60000, I erases / writes without any problem

But when we try to write/erase beyond 0x6ffff or higer addres it erases/writes on our boot loader and ubl which is kept in the first block

we have customize the u-boot 1.2.0 which came with DM355evm board.

Thanks

Thalib

  • 0
    Intellectual 580 points

    Please refer the log below for the above issue

     


    U-Boot 1.2.0-gb7cad7ae-dirty (May 22 2010 - 12:13:16) Alpha

    DRAM:  256 MB
    NAND:  thalib : board_nand_init
    NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
    Bad block table found at page 131040, version 0x01
    Bad block table found at page 131008, version 0x01
    64 MiB
    *** Warning - bad CRC or NAND, using default environment

    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock :- 216MHz
    DDR Clock :- 133MHz
    => nand write 0x82000000 0x60000 0x4000

    NAND write: device 0 offset 0x60000, size 0x4000
     16384 bytes written: OK.
    => reset
    .DM35x initialization passed!
    TI UBL Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000019.
       DONE
    Jumping to entry point at 0x81080000.


    U-Boot 1.2.0-gb7cad7ae-dirty (May 22 2010 - 12:13:16) Alpha

    DRAM:  256 MB
    NAND:  thalib : board_nand_init
    NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
    Bad block table found at page 131040, version 0x01
    Bad block table found at page 131008, version 0x01
    64 MiB
    *** Warning - bad CRC or NAND, using default environment

    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock :- 216MHz
    DDR Clock :- 133MHz
    => nand write 0x82000000 0x60000 0x5000                    ========== > now wite above 60000+4000

    NAND write: device 0 offset 0x60000, size 0x5000
     20480 bytes written: OK
    => reset
    .DM35x initialization passed!
    TI UBL Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    No valid boot image found!
    NAND Boot failed.
    Aborting...

  • 0 in reply to Thalib
    Prodigy 50 points

    The board uses dm355 ic  and works smoothly for sometime. After some days  this is what it happens

    DM35x initialization passed!
    TI UBL (Modified by Silvan) Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000019.
    Jumping to entry point at 0x81080000.


    U-Boot 2010.06 (Aug 17 2010 - 14:56:30)

    Cores: ARM 216 MHz
    DDR: 133 MHz
    I2C: ready
    DRAM: 128 MiB
    NAND: 128 MiB
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    *** Warning - bad CRC or NAND, using default environment

    Net: dm9000
    Hit any key to stop autoboot: 3 2 1 0
    ERROR: resetting DM9000 -> not responding
    dm9000 not found at 0x04000000 id: 0x2b2a2928
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    U-BOOT-SHIV $

    How to solve this  *** Warning - bad CRC or NAND, using default environment      PROBLEM


    Kindly reply

  • 0 in reply to akshay hublikar
    Expert 1555 points

    Hello Akshay !

    As far as I remember, the " * * * Warning - bad CRC..." message appears when u-boot environment is not set (initial).

    In my case, this message disappeared when the environment variables were saved via "saveenv" command.

    Try to use
    saveenv

    Hope, It helps.
    Sorry, if not.
    best regards, senchuss

  • 0 in reply to Arseniy Platonov
    Prodigy 50 points

    Actually i have many such boards , all are working fine, only very few are giving problems.

    Is it a problem with nand flash.

  • 0 in reply to akshay hublikar
    Guru 31670 points

    I have also seen the same issues before on DM365 IPNC with a Samsung NAND. I can investigate the issue if you can share the board. Contact me @ renjith.thomas@pathpartnertech.com