sorry about my wrong post

Hello,Nothing happens after I run the tftp command. It just returns a new u-boot prompt with no warnings at all.Is there a tftp variable in u-boot that has to be set inorder for the tftp to work.

From: simrangill999@hotmail.com To: vickylinuxer@gmail.com Date: Sun, 17 Jul 2011 18:40:55 -0700 CC: u-boot@lists.denx.de Subject: Re: [U-Boot] U-BOOT TFTP

Hello,Nothing happens after I run the tftp command. It just returns a new u-boot prompt with no warnings at all.

Date: Sat, 16 Jul 2011 06:01:27 +0000 Subject: Re: [U-Boot] U-BOOT TFTP From: vickylinuxer@gmail.com To: simrangill999@hotmail.com CC: u-boot@lists.denx.de

Hi

Can u give a clear log about uboot version and what u getting after executing "tftp 1000000 /tftpboot/uImage".

Regards Vignesh Rajendran

_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Hi simran,

you should really provide us with more data to give us even a remote chance of helping you. What board do you use, what CPU is it, what U-Boot version do you use? Are you doing a custom U-Boot port or "simply use a well-supported U-Boot configuration from mainline"?

Hello, This is the ouput when I do tftp or try the ping with the environment set accordingly. Could it possibly be one of the configuration files such as the RCW (reset configuration word) but I cannot change this file withno tftp connection.Any help would be great. Thank you.

To be honest, I do not understand what a RCW has got to do with a tftp transfer.

=> ping 192.168.1.1 ping failed; host 192.168.1.1 is not alive => ping 192.168.1.129 ping failed; host 192.168.1.129 is not alive => tftp 1000000 /tftpboot/uImage => tftp 0x1000000 /tftpboot/uImage => => printenv

ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr bootdelay=10 baudrate=115200 loads_echo= rootpath=/opt/nfsroot loadaddr=1000000 netdev=eth0 uboot=u-boot.bin tftpflash=tftpboot $loadaddr $uboot; protect off 0xeff80000 +$filesize; erase 0xeff80000 +$filesize; cp.b $loadaddr 0xeff80000 $filesize; protect on 0xeff80000 +$filesize; cmp.b $loadaddr 0xeff80000 $filesize consoledev=ttyS0 ramdiskaddr=2000000 fdtaddr=c00000 fman_ucode=0xEF000000 eth1addr=00:04:9F:02:01:FD eth2addr=00:04:9F:02:02:FD eth3addr=00:04:9F:02:03:FD eth4addr=00:04:9F:02:04:FD eth5addr=00:04:9F:02:05:FD eth6addr=00:04:9F:02:06:FD eth7addr=00:04:9F:02:07:FD eth8addr=00:04:9F:02:08:FD eth9addr=00:04:9F:02:09:FD bootfile=uImage ramdiskfile=rootfs.ext2.gz.uboot fdtfile=p4080ds.dtb

bdev=sda3

bank4=mw.b 0xffdf002c 0x40; mw.b 0xffdf002d 70; mw.b 0xffdf0010 0; mw.b 0xffdf0010 1

gatewayip=192.168.1.1

bootcmd=bootm e8020000 e9300000 e8800000

ipaddr=192.168.1.145

serverip=192.168.1.129

bootargs=root=/dev/mtdblock0 rw console=ttyS0,115200 ethaddr=00:C0:F7:02:01:FD stdin=serial stdout=serial stderr=serial

ethact=FM1@DTSEC1

Environment size: 1500/8188 bytes

Where do all those empty lines in the log come from? Are you sure that the setting for ethact is correct? Do you really have 8 network devices but only 4 mac addresses assigned to them? I.e. usually we have "ethaddr", "eth1addr", etc. for the network interfaces - I've never seen such a combinmation as in your logs.

Do you have the variable "netmask" setup correctly?

In short, it seems like there is a lot of confusion in your setup. Does U-Boot work for you at all or is the network failure only "one of the problems"?

Cheers Detlev

Hello all, I really appreciate all of your replies and sorry for not being responsive for sometime. But I am glad to say that I was able to flash new u-boot along with fman ucode and rcw. I am using p4080DS dev board from freescale and the rcw is important in terms of which ports to be enabled upon boot. I ran into all of these problems because the ltib version I was using was not compatible with my version of the board. Wish I knew this earlier but there was no way for me to find this out. Neways all is up and running and thanks once again for providing all the help. Sincerely,Simran

Date: Thu, 21 Jul 2011 10:24:07 +0000 Subject: Re: [U-Boot] U-BOOT TFTP From: vickylinuxer@gmail.com To: simrangill999@hotmail.com CC: u-boot@lists.denx.de

Hello simran

The things u have to do is check your network connectivity between board and target .If it is not working after that, make a clean u-boot compilation again with basic configuration(no confusing) of your board header file and port again.

Regards

Vignesh Rajendran