Hey Aditya, You can use the bootarguments as setenv serverip <tftp server ip address> setenv serverip <tftp board ip address> setenv bootcmd tftp 0x80700000 uImage_teleste \;bootm 0x80700000
Please make sure that the tftp server and board ip address are in the same subnet mask. Remarks on you confusion: Also we are confused on 1) can we boot the kernel through tftp without copying the image into the memory of target?? or we necessarily have to copy the image into the memory of target and then boot?? ---------------- Whatever might be the source or uImage(flash/nfs/tftp), the image will be copied to DDR first and un-compressed there and then the board will boot from there. 2)we have searched on booting via tftp...and we found that lot of people use following command:: tftp 0x80700000 uImage will this command write the new "uImage" to 0x80700000 on the target? what is the address 0x80700000 pointing to? will my orignal kernel get affected if we write to this address? ------------------------------- This command will write the uImage to location 0x80700000 of DDR. Your original kernel is present in NAND/NOR flash of 6446 EVM. The image in flash will also be copied into the same location of DDR before booting. Using TFTP you will copy the uImage into 0x80700000 location of DDR and flash where your actual image is present is no-where coming into picture. So, in case of TFTP instead of flash you are copying the image from the tftp server. This is the only difference. Subhranil. From: davinci-linux-open-source-bounces+subhranil.choudhury=ittiam....@linux.davincidsp.com [mailto:davinci-linux-open-source-bounces+subhranil.choudhury=ittiam....@linux.davincidsp.com] On Behalf Of Aditya Barawkar Sent: Thursday, February 03, 2011 2:42 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: boot through tftp hi, We are using a DM6446 EVM. We have compiled a kernel for the board, in which we enabled various drivers required(through make menuconfig) Now we want the kernel to be booted via tftp(unlike what is default booting from flash) and the filesys will be nfs as usual. the bootargs for the tftp are as follows...(as given in the texas getting started guide) EVM # setenv bootcmd 'dhcp;bootm' EVM # setenv serverip <tftp server ip address> EVM # setenv bootfile <name of kernel image> EVM # setenv rootpath <root directory to mount> EVM # setenv nfshost <ip address of nfs host> EVM # setenv bootargs video=davincifb:vid0=720x576x16, 2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=120M but when we boot the board we get following error: Unknown command 'dhcp' - try 'help' and the kernel boots from flash as default. TirDavinci_EVM# printenv bootdelay=3 baudrate=115200 ethaddr=ff:ff:ff:ff:ff:ff ipaddr=192.168.0.51 nfshost=10.42.43.1 rootpath=/home/aditya/workdir/filesys serverip=10.42.43.1 bootargs=video=davincifb:vid0= 720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=NTSC console=ttyS0,11M bootfile=/var/lib/tftpboot/uImage bootcmd=dhcp;bootm <<<---------------For boot through tftp (refering to section 4.7 , A.4.4 in getting started guide..sprue66d.pdf) stdin=serial stdout=serial stderr=serial Environment size: 526/8188 bytes TirDavinci_EVM# boot Unknown command 'dhcp' - try 'help' <<<---------------dhcp command not recognised by uboot ## Booting image at 02050000 ... Image Name: Linux-2.6.10_mvl401-davinci_evm Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1324188 Bytes = 1.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting Davinci linux kernel... Uncompressing Linux.................................................................................................. done, booting thee and the orignal kernel is booted... Also we are confused on 1) can we boot the kernel through tftp without copying the image into the memory of target?? or we necessarily have to copy the image into the memory of target and then boot?? 2)we have searched on booting via tftp...and we found that lot of people use following command:: tftp 0x80700000 uImage will this command write the new "uImage" to 0x80700000 on the target? what is the address 0x80700000 pointing to? will my orignal kernel get affected if we write to this address? thanks in advace!
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
