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

preparing SD card for booting from

mans
Expert 1005 points

I have a sd card that has the following files in it:

23/11/2011 14:30 229 boot.cmd

23/11/2011 14:30 301 boot.scr

23/04/2012 16:30 164 boot.txt

23/11/2011 14:30 68,796 MLO

23/11/2011 14:30 244 README.boot.scr

23/11/2011 14:30 126,399 top_ti814x_evm.png

23/11/2011 14:30 185,044 u-boot.bin

23/11/2011 14:30 2,570,080 uImage

23/11/2011 14:30 1,711 windows_users.htm

(This is the SD card which shipped with EVM). I copied all of these files into a 32GByte Sd card, but when I place this new SD card into my system it doesn't work.

What is the problem?

Should I use a smaller SD card? Should I format it in a specific way?

  • 0
    Intellectual 260 points

    On the SD card with EVM,  There are 2 file system partition.

    One is you  find, have u-boot.bin, uImage, MLO,   another is a linux file system, it's can't display on explorer on Windows.


    Follow the DM814x_EZ_Software_Developers_Guide, You can make the SD card, or disk-copy the SD card by Ghost.

  • 0 in reply to xue
    Expert 1005 points

    Thanks. I will do.

    But why I can not boot using mlo and uboot? I copied them into a new SD card? 

  • 0 in reply to mans
    Intellectual 260 points

    I don't know the reason exactly.

    I think some special informat is written on SD card by SD make tools, such as position and size of partitions,  hidden cluster...

    When you copy the mlo and uboot, the special information is lost.

  • 0 in reply to xue
    Intellectual 540 points

    I think that the order of the files on the SD card matters. I have had success by formatting a card, and copying the MLO, u-boot.bin, and uImage, in that order. But if I delete, rename, or copy over the files, it will eventually stop working, even though I'm ending up with a set of boot files that should be valid.

    I suspect that the boot code in the 8148 is very limited and does not implement a full FAT filesystem reader. It probably just scans the first few entries in the FAT using simplified code, and gives up if it can't find MLO.

    That's just a guess, though. 

  • 0 in reply to Brett Kuehner
    Intellectual 465 points

    If you're running fdisk to create the partition, you can follow these steps to create a bootable SD card.

    * n
    * p
    * 1
    * <enter>
    * +100M
    * t
    * C
    * a
    * 1

    That will create a new primary partition, numbered 1, starting at the beginning sector, 100 megabytes in size (feel free to modify that), set the partition type to FAT32 (LBA), and mark it active/bootable.  Write the partition table with 'w' and it should be set up correctly.  'mkfs.vfat' to create the actual filesystem, then copy your files in.

    32GB is larger than I've personally used (I've tried up to 16gb) but that shouldn't be a problem.  I would probably avoid creating the FAT32 partition as the full size of the disk though.