Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-11-18 Thread akdas75
Hi I have submitted the patch http://patchwork.ozlabs.org/patch/199895/ It required little more fixes in OMAP3 SPI code. Now its working like a charm There are no changes need to be done in enc28j60 code. Attach logs for your reference http://old.nabble.com/file/p34695543/working.cap working.c

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-11-12 Thread akdas75
Hi Anatolij and Wolfgang Denk I will submit the patches soon. I am reading the links to submit patches. The OMAP3 SPI patch is required for proper functioning of that subsytem. I studied the linux driver and the TRM to arrive at this changes. I wonder how these changes were not incorporated by

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-11-09 Thread Anatolij Gustschin
Hi Ajoy, On Thu, 8 Nov 2012 19:26:28 -0800 (PST) akdas75 wrote: > > Hi Anatolij and Wolfgang Denk > > I have solved the problem. > There are some "must" changes in omap3_spi.c to make it working. Otherwise > it will not be behave in the expected way. Okay, thanks for reporting. > There are

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-11-08 Thread akdas75
Hi Anatolij and Wolfgang Denk I have solved the problem. There are some "must" changes in omap3_spi.c to make it working. Otherwise it will not be behave in the expected way. There are also few changes in enc28j60.c file to make it more stable. I have attached the snapshot of both ping and tftp.

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-11-01 Thread akdas75
Hi I analyzed the code and put some prints to find the below mentioned behavior. The ARP packet is being received by ENC28J60 but when it reaches the software pkt format is not correct. A 0 is being appended to the packet. After analysis I found this errata mentioned in ENC28J60 errata sheet i

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-30 Thread akdas75
Hi As per your suggestion I tried 2012.10 Still the result is same. But it shows receive length is zero. I have attached the logs I have attached the changes to make ethernet work. As I am new to this forum I hope you said me to reply to this mailing list. Ajoy http://old.nabble.com/file/p34

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-29 Thread akdas75
hi No I dont have any firewall running. I have enabled to receive all packets [] i am using the uboot version 2011.03 with the following changes. But i think it will not affect the ping functionality. Any help. I will try putting more logs and pointing the issue. attached is the patch Ajoy

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-28 Thread Wolfgang Denk
Dear akdas75, In message <34610904.p...@talk.nabble.com> you wrote: > > I generate a macid from uboot/tools/gen_eth_addr. > Still the ping says "host not alive" > > I have attached the uboot log > and also the wireshark snapshot on the host > > host : 192.168.1.101 > development board : 192.168

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-28 Thread akdas75
hi Anatolij I tried your suggestion I generate a macid from uboot/tools/gen_eth_addr. Still the ping says "host not alive" I have attached the uboot log and also the wireshark snapshot on the host host : 192.168.1.101 development board : 192.168.1.100 Ajoy http://old.nabble.com/file/p34610904

Re: [U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-27 Thread Anatolij Gustschin
Hi, On Fri, 26 Oct 2012 22:29:32 -0700 (PDT) akdas75 wrote: > > Hi http://old.nabble.com/file/p34608548/uboot-log.rtf uboot-log.rtf > > I am using beagle board C4 with zippy expansion board. > I am able to do NFS at the kernel level. > I want to o tftp at the u-boot level. > my beagle board i

[U-Boot] ping failed; host 192.168.1.101 is not alive

2012-10-27 Thread akdas75
Hi http://old.nabble.com/file/p34608548/uboot-log.rtf uboot-log.rtf I am using beagle board C4 with zippy expansion board. I am able to do NFS at the kernel level. I want to o tftp at the u-boot level. my beagle board is connected to the host via cross ethernet cable. the phy chip is enc28j60.