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

sdk 5.02.02.60 question on tftpboot in uboot

Mohsen Khayami
Mastermind 22391 points

Champs

my customer use the script to setup his Sd card and stuff with the SDK 5.02.02.60 and a strange thing happen: when the tftpboot run it asked for a file name fc-boot.elf so not sure where this file name is coming from. Below are the setenv and below that is the bootcmd running. I am not sure why it is asking for the fc-boot.elf file any suggestions that would be great.

TI8168_EVM#printenv

verify=yes

ramdisk_file=ramdisk.gz

loadaddr=0x81000000

script_addr=0x80900000

loadbootscript=fatload mmc 1 ${script_addr} boot.scr

bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${scri

pt_addr}

ethact=DaVinci EMAC

ethaddr=00:02:c5:11:11:c5

netmask=255.255.192.0

ipaddr=192.168.192.204

bootdelay=4

baudrate=115200

oldbootargs=console=ttyO2,115200n8 rootwait rw mem=256M earlyprintk notifyk.vpss

m3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=

192.168.192.23:/home/vbox/Desktop/vbox_shared/targetfs ip=dhcp

bootargs=console=ttyO2,115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_

sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=192

.168.192.166:/home/vbox/Desktop/vbox_shared/targetfs ip=dhcp

autoload=no

oldserverip=192.168.192.23

serverip=192.168.192.166

oldbootfile=uImage-dm816x-evm.bin

bootfile=uImage-dm816x-evm.bin

oldbootcmd=dhcp;setenv serverip 192.168.192.23;tftpboot;bootm

bootcmd=dhcp;setenv serverip 192.168.192.166;tftpboot;bootm

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2010.06 (Nov 18 2010 - 22:36:59)

 

Environment size: 1119/8188 bytes

TI8168_EVM#boot

BOOTP broadcast 1

DHCP client bound to address 192.168.192.177

Using DaVinci EMAC device

TFTP from server 192.168.192.166; our IP address is 192.168.192.177

Filename 'fc-boot.elf'.

Load address: 0x81000000

Loading: *

TFTP error: 'File not found' (1)

Not retrying...

Wrong Image Format for bootm command

ERROR: can't get kernel image!

TI8168_EVM#

 

Regards

Mohsen

  • 0
    TI__Genius 9510 points

    Try setting the bootcmd as follows

     

    bootcmd= dhcp;tftp 81000000 <filename>;bootm

  • 0
    Intellectual 855 points

    Does the board boot from SD? If yes, try use boot.src. Generate the file and copy it to the SD. It starts automatically.

    From DM816x_C6A816x_AM389x_PSP_U-Boot.pdf page 21:

    ENV on SD card using a script
    U-Boot environment variables can be modified using U-Boot scripts. The scripts can be used to modify and even
    over-ride the various parameters like bootargs, TFTP serverip etc.
    Generation of the scripts is done with the help of the mkimage tool which can be found under the tools directory of
    the U-Boot source. The mkimage binary gets generated whenever any U-Boot image is built.
    Once the  mkimage  binary generated, create a text file named  boot.txt  with the U-Boot commands that would
    normally be executed manually at the U-Boot prompt.
    Example text file named boot.txt


    setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p2 mem=128M
    rootwait'
    setenv bootcmd 'mmc init; fatload mmc 1 0x81000000 uImage; bootm
    0x81000000'
    boot


    Now use the following command to generate the script named boot.scr

     

    It works for me ok.

    - Robert


    mkimage -A arm -O linux -T script -C none -n TI_script -d boot.txt
    boot.scr


    The file boot.scr can now be executed from U-Boot using the source command to execute all the commands present
    in it.