• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 1059 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.

DM365 SD card boot method

Kumar Vale
Intellectual 270 points

Hello  

Is there is another way of booting the DM365 leopard board from SD card as I am having problem with the method below, http://processors.wiki.ti.com/index.php/SD_card_boot_and_flashing_tool_for_DM355_and_DM365

I found this link but talk about SD card boot, but didn’t work as I think it assume the boot software still in the NAND flash. https://www.ridgerun.com/developer/wiki/index.php/RidgeRun_SDK_Technical_FAQ#No_icache_command_at_uboot

Thank you

Kumar

  • 0
    Expert 2995 points

    sudo ./dm3xx_sd_boot format /dev/sdf1

  • 0
    TI__Expert 5215 points

    Kumar,

    Have you resolved this issue?

    It looks like you need to set the on-board DIP switches for SD Boot Mode. Look in section 2.21 of the Leopardboard 365 Hardware Guide. Make sure that you are set to '010' and not '000'.

  • 0 in reply to Michael Risley
    Intellectual 270 points

    Hello Michael,

     

    I think I have solved my first issue but I cannot verify this till I boot from SD card.

    I did set the dip settings to SD boot mode(010). Do you see anything wrong in the log below?

    [root@tools ~]# export PATH=$PATH:./bin.x86

    [root@tools ~]# cd /media/809A-4AF4/dm3xx_sd_boot-6.1

    [root@tools dm3xx_sd_boot-6.1]# cd dm3xx_sd_boot-6.1

    [root@tools dm3xx_sd_boot-6.1]# mount -t vfat /dev/sda1 /media/sdcard

    mount: /dev/sda1 already mounted or /media/sdcard busy

    mount: according to mtab, /dev/sdd1 is already mounted on /media/sdcard

    [root@tools dm3xx_sd_boot-6.1]# sudo ./dm3xx_sd_boot format /dev/sdd

    cleaning SD card

    1000+0 records in

    1000+0 records out

    1024000 bytes (1.0 MB) copied, 0.760558 s, 1.3 MB/s

    Disk /dev/sdd: 1015 cylinders, 63 heads, 62 sectors/track

    sfdisk: ERROR: sector 0 does not have an msdos signature

    /dev/sdd: unrecognized partition table type

    Old situation:

    No partitions found

    New situation:

    Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

    Device Boot Start End MiB #blocks Id System

    /dev/sdd1 * 0+ 40- 41- 41012+ b W95 FAT32

    /dev/sdd2 * 40+ 1935- 1896- 1941282 83 Linux

    /dev/sdd3 0 - 0 0 0 Empty

    /dev/sdd4 0 - 0 0 0 Empty

    Successfully wrote the new partition table

    Re-reading the partition table ...

    mkfs.vfat 3.0.1 (23 Nov 2008)

    0+0 records in

    0+0 records out

    0 bytes (0 B) copied, 0.000200782 s, 0.0 kB/s

    0+1 records in

    0+1 records out

    19 bytes (19 B) copied, 0.000127263 s, 149 kB/s

    total 15000

    -rwxr-xr-x. 1 root root 15360000 2011-09-28 01:47 dm3xx.dat

    SD card /dev/sdd formatted

    10000+0 records in

    10000+0 records out

    10240000 bytes (10 MB) copied, 1.09671 s, 9.3 MB/s

    dm3xx_boot_data_addr=0x0a2000

    Image dm3xx_boot_rec:a1aced00 100 3c 511 0 0 0 0 a2000

    10000+0 records in

    10000+0 records out

    10240000 bytes (10 MB) copied, 1.15872 s, 8.8 MB/s

    dm3xx boot record is written

    Please reinsert the card for auto mounting or mount it manually

    [root@tools dm3xx_sd_boot-6.1]# make install

    ./dm3xx_sd_boot data

    copying data to

    Writing /media/dm3xx-boot/dm3xx.dat

    000200-006724, 25892 bytes <- sdcard_flash/sdcard_flash_DM36x.bin

    008000-008200, 512 bytes <- test pattern 1 2 3

    010000-015000, 20480 bytes <- original/UBL_DM36x_NAND.bin

    020000-045308, 152328 bytes <- original/u-boot-1.3.4-dm365_evm.bin

    060000-2547c8, 2049992 bytes <- original/uImage-dm365

    400000-6740c7, 2572487 bytes <- original/ramdisk.gz

    syncing

    DM355 boot data copied in data file /media/dm3xx-boot/dm3xx.dat on

    Filesystem 1K-blocks Used Available Use% Mounted on

    /dev/sdd1 40365 15001 25365 38% /media/dm3xx-boot

    [root@tools dm3xx_sd_boot-6.1]#

    Thanks

    Kumar

  • 0 in reply to Kumar Vale
    Intellectual 270 points

     

    The LEDs LED1 and LED2 are on, meaning something happening in the boot but I don’t think the NAND getting programmed, I don’t see anything on the terminal –any suggestion?

  • 0 in reply to Kumar Vale
    Prodigy 20 points

    Hi Kumar,

    First of all, please make sure you use a normal SD card (capacity <= 2GB). The SD boot software doesn't support SDHC.

    The Leopardboard connects the Write Protect pin of the NAND flash to a GPIO of the DM365. This pin should pull low for NAND update. We have made some modifications of the original software, and posted it here:

    https://www.leopardimaging.com/uploads/dm3xx_sd_boot-6_leopard.tgz

    with a readme file: https://www.leopardimaging.com/uploads/sd_boot_readme.txt

    Please follow the instructions and let me know how it goes.

    -Leon

  • 0 in reply to Leon Luo
    Intellectual 270 points

    Hello Leon,

    I am getting the following errors with leopard imaging method (https://www.leopardimaging.com/uploads/sd_boot_readme.txt),

    make[1]: arm_v5t_le-gcc: Command not found
    make[1]: *** [DM36x/boot.o] Error 127
    make[1]: Leaving directory `/media/809A-4AF4/dm3xx_sd_boot-6_leopard/dm3xx_sd_boot-6_leopard/sdcard_flash'
    make: *** [all] Error 2

    Kind regards

    Kumar

  • 0 in reply to Kumar Vale
    Prodigy 20 points

    It requires Montavista pro 5.0 to compile. Please add the cross compile path:

    export PATH=MONTAVISTA_COMPILER_PATH:$PATH