• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 6657 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.

HELP: Warning - bad CRC or NAND, using default environment

Michael Pawluch
Prodigy 20 points

I have recently unpacked an AM3517EVM that I had on the shelf for quite a while.  It came loaded with the Arago Project versin of Linux.  Whenever I boot it up,from the internal rom, I get:


Texas Instruments X-Loader 1.44 (Dec  8 2009 - 22:58:46)
Starting OS Bootloader...


U-Boot 2009.08 (Dec 08 2009 - 23:00:10)

AM35xx-GP ES1.0, L3-165MHz
am3517evm board + LPDDR/NAND
I2C:   ready
DRAM:  256 MB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

 

Even when I use an angstrom Distribution from an SD CARD I get the same results.

Texas Instruments X-Loader 1.46 (May  4 2011 - 00:55:20)
Starting X-loader on MMC
Reading boot sector

223696 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11-dirty (May 04 2011 - 00:54:46)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

ALSO:

the Board does not seem to register any of the boot scripts that I place into the boot.scr file (these come pre-assembled with the angstrom distribution) and i imagine that this is due to the above warning.  HOW DO I GET RID OF IT?????

  • 0
    TI__Intellectual 1250 points

    Is the board capable of saving the current environment back to NAND?  I.e., does the 'saveenv' command work in u-boot.

    Greg

  • 0
    TI__Expert 6735 points

    Michael:

    This means that your board does not have a valid u-boot environment stored in NAND flash so

    it is using defaults.  You can see what the defaults are if you stop the boot at u-boot prompt and

    do the printenv.   If needed, you would enter setenv commands to setup your u-boot environment

    the way you need it.  The content of that depend on how you want to boot up (kernel from SD Card,

    Ethernet, Nand,  file system on SD Card, network or Nand...) 

    Finally do a saveenv cmd to save the u-boot environment to NAND flash.  When you reboot you

    will not have the warning msg.

    Our EZSDK has a setup script that performs the u-boot parameter setup for you.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sdk/AM3517/latest/index_FDS.html

    Regards,

    Michael T

     

     

  • 0 in reply to Michael T
    Prodigy 20 points

    Michael:

    Your reply is awesome, makes perfect sense. Since I am constantly going to be changing environments, (Several different projects) it makes more sense to have the boot environment located with the particular program on SD card, rather than have it "frozen" in nand,   I have used that SDK , however, my aims were to be able to have a fully self contained system on sd card.  Is there any way of redirecting the setup to load an environment from an sd card automatically on uboot?

  • 0 in reply to Michael Pawluch
    TI__Expert 6735 points

    Michael:

    You can erase the u-boot env from NAND from U-Boot prompt, like this:

    U-Boot # nand erase 0x260000 0x20000

    Then the default u-boot parametrs will be used.  depending on your U-Boot

    version, this should allow you to store the u-boot environment setup

    commands in a file names uEnv.txt in boot sector of SD Card.

    Regards,

    Michael T