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

[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/p34620403/uboot.txt uboot.txt 
http://old.nabble.com/file/p34620403/uboot.patch uboot.patch 



akdas75 wrote:
> 
> 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
> 
> 
> 
> akdas75 wrote:
>> 
>> 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/uboot_log_1.txt uboot_log_1.txt 
>> http://old.nabble.com/file/p34610904/snap_wireshark_host.JPG
>> snap_wireshark_host.JPG 
>> 
>> 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 is connected to the host via  cross ethernet cable.
>>> the phy chip is enc28j60. 
>>> when i ping  the host it says host not alive.
>>> 
>>> i have attached the env variables
>>> 
>>> please help
>>> 
>>> 
>> 
>> 
>  http://old.nabble.com/file/p34615656/u-boot.patch u-boot.patch 
> 

-- 
View this message in context: http://old.nabble.com/ping-failed--host-192.168.1.101-is-not-alive-tp34608548p34620403.html
Sent from the Uboot - Users mailing list archive at Nabble.com.