• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 98 subscribers
  • Views 1094 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.

DM37x eval board SD card issues

Dennis Kerrisk
Prodigy 160 points

I just recieved a DM37x eval board I am having issues with it.  And I don’t want to make any changes to the SD card. And can’t seem to make a working copy of it.  I bought an 8 gig SD card, it won’t boot. I get this message:

Texas Instruments X-Loader 1.46 (Mar 24 2011 - 20:21:25)

ONENAND Flash Unsupported

OneNAND Unsupported !

X-Loader hangs

 

Is there a special kind of SD card I need to get to make a bootable copy? If so what kind? I can’t read what kind came with the board, because of the labels.

I have tried just putting the uboot partition on a 2 gig SD card, and it won’t even try to boot. What am I doing wrong?

 

Also the TI SD card gets lots if errors on boot up during uboot. Is this normal?

U-Boot 2009.11 (Mar 24 2011 - 20:27:06)

 

AM37x/DM37x-GP ES2.1, CPU-OPP2 L3-165MHz

OMAP3 EVM board + LPDDR/NAND

I2C:   ready

DRAM:  256 MB

NAND:  512 MiB

err_loc=2509

err_loc=-1144

err_loc=-1311

err_loc=-2375

err_loc=3924

err_loc=3686

err_loc=959

err_loc=-3521

err_loc=3535

err_loc=2218

err_loc=-1854

err_loc=-1959

err_loc=1141

err_loc=559

err_loc=-860

err_loc=-2114

 

 

  • 0
    Guru 26430 points

    I think your platform uses a 3 partition SD Card. Some online reference.

    http://processors.wiki.ti.com/index.php/Creating_filesystems_on_removable_media

    Your board should have come with disc with a lot of packages on it. There is usually a User Guide buried in among all the packages that describes how to build a SD Card from the included pre-built images. I think the contents are also online as well. One for Linux and one for Android.

    Googling about gave a way to clone a card. I have never used this command so take this with a grain of salt.

    dd if=/dev/sda of=/dev/sdb

    Assumes that sda and sdb are the source and destination cards on two card readers. Be very careful that sda and sdb are your SD cards and not your hard drive. You may have to unmount both cards first. I imagine that the cards should be the same size.

     

  • 0 in reply to Norman Wong
    Prodigy 160 points

    I used dd to copy it to another 8 gig SD card and when it boot I get this error message:

    Texas Instruments X-Loader 1.46 (Mar 24 2011 - 20:21:25)

    ONENAND Flash Unsupported

    OneNAND Unsupported !

    X-Loader hangs

     

     

  • 0 in reply to Dennis Kerrisk
    Guru 26430 points

    Oops. Gave you the wrong link on the TI wiki. Should be:
    http://processors.wiki.ti.com/index.php/How_to_Make_3_Partition_SD_Card

    The EVM product page says they used a 4GB SD card.
    http://focus.ti.com/docs/toolsw/folders/print/tmdsevm3730.html
    Also states that all the SW is on the SD Card. No disc.

    Did the 'dd' command copy all 3 partitions? Handy command if it did.

    That's all I got. Hopefully some DM37xx EVM guys can comment on the SD Card and the NAND error messages.

     

  • 0 in reply to Norman Wong
    Prodigy 160 points

    Yes the dd command copied all 3 partitions. I verified on my linux machime.

  • 0 in reply to Dennis Kerrisk
    TI__Expert 4590 points

    Not all cards - even though capacity is same - are same. While 'dd' does work for normal data, it fails for bootable cards.

    Since you have a linux machine, I suggest this sequence:

    • Format the new card by using the script included in the SDK. (I don't have the card handy with me now; but the name of script should be quite obvious).
    • Manually copy  the contents of BOOT partition in this sequence - MLO, u-boot.bin, boot.scr, uImage (and the rest)
    • As root (or via sudo) copy the contents of the filesystem partition. (You could even save the contents in a tarball - to be extracted later with "root" permissions).
    • Copy the contents of 3rd partition.
  • 0 in reply to Sanjeev Premi
    Prodigy 160 points

    I tried that too. I got the exact same results as I did using dd.

  • 0 in reply to Dennis Kerrisk
    Guru 26430 points

    A somewhat related thread:

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/29342.aspx

    That person had some marginal timing problems on a custom board. Although your board is not custom, perhaps your board is "aging".

    Maybe try a different class or manufacturer of card.

     

  • 0 in reply to Norman Wong
    Prodigy 160 points

    I have already treid a SanDisk and a toshiba card. Neither one worked. The toshibe got the OneNand Error. The SanDisk did nothing at all.

     

  • 0 in reply to Dennis Kerrisk
    Guru 26430 points

    I think the X-Loader source for your platform is here:

    http://arago-project.org/git/projects/?p=x-load-omap3.git;a=tree

    Relevant bits in these files:

    lib/board.c - see start_armboot()
    board_omap3evm/omap3evm.c - see nand_init()
    drivers/onenand.c - see onenand_chip()

    The bootup fails when a specific type of One NAND is not found. Why the SD Card would affect NAND detection? I don't know. Are there any boot switches you can experiment with. Maybe you can force it to not look at the One NAND. I am assuming that all this NAND memory is on-board memory. I don't know if it is possible but the code might be addressing SD memory as NAND.

     

  • 0 in reply to Norman Wong
    Prodigy 160 points

    Without changing any of the switches, I have one card that sort of works. One card that gets the oneNand error, and one card that does nothing at all. I am really just trying to get any second card to work.

  • 0 in reply to Dennis Kerrisk
    Guru 26430 points

    Here's another somewhat related thread:

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/30212.aspx

    In the thread, they use fdisk to compare the SD card geometries. A smaller size for the first partition seemed to help that guy.

    X-Loader is the MLO file on the SD Card. The Card that fails with a "X-Loader hangs" message implies that the ROM Boot code did load the X-Loader from the SD Card. Just the weirdness with the One Nand. The card that does nothing at all suggests the ROM Boot code didn't load the X-Loader from SD.

    Unsure who owns the Boot ROM code. Maybe Mistral, the board manufacturer, might have the answers.