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

[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 anyone.

Ajoy


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.
> There are also few changes in enc28j60.c file to make it more stable.
> I have attached the snapshot of both ping and tftp.
> 
> Please let me know if I can submit the changes as patch because they are
> required
> for proper working of the omap3 SPI.
> http://old.nabble.com/file/p34659079/ping_success.cap ping_success.cap  
> 
> Ajoy
>  
> 
> 
> 
> akdas75 wrote:
>> 
>> 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 is
>> not applied for the initial case
>> (for the first packet). Later on it is fine.
>> I have made the changes and I need to test it today night after office.
>> 
>> Module: Memory (Ethernet Buffer) The receive hardware may corrupt the
>> circular
>> receive buffer (including the Next Packet Pointer and receive status
>> vector fields) when an even value
>> is programmed into the ERXRDPTH:ERXRDPTL registers.
>> Work around
>> Ensure that only odd addresses are written to the ERXRDPT registers.
>> Assuming that ERXND contains
>> an odd value, many applications can derive a suitable value to write to
>> ERXRDPT by subtracting
>> one from the Next Packet Pointer (a value always ensured to be even
>> because of hardware padding)
>> and then compensating for a potential ERXST to ERXND wraparound. Assuming
>> that the receive
>> buffer area does not span the 1FFFh to 0000h memory boundary, the logic
>> in Example 1 will ensure that
>> ERXRDPT is programmed with an odd value
>> 
>> Are you aware of any such change required in the ENC28J60  uboot code. 
>> Kindly let me know if anybody has faced such issue
>> 
>> 
>> akdas75 wrote:
>>> 
>>> 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-tp34608548p34672288.html
Sent from the Uboot - Users mailing list archive at Nabble.com.