Ethernet port not able to get response for ping command (used ti8148 processor and psp version 04.01.00.07)

Sudheer,

Are you able to ping the host PC from u-boot?

BR
Pavel

no, I am not able to ping from u-boot.

I have tried using the commands like

# setenv autoload no

# dhcp

and pinged the host ip but it was saying it is not alive.

Sudheer,

What is the mode you are using: G/MII, RMII or RGMII?

See the below e2e thread for more info:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/358123.aspx

BR
Pavel

I am using RGMII.

Issue in the link you mentioned was with GMII, as his interface was GMII and in evm.c file he corrected for GMII and in my case we are using RGMII only.

I even tried to set to GMII and ping but no luck. Can you pleas once go through all the command and response which I mentioned to get any clue.

command 1:

TI8148_EVM#setenv autoload no

TI8148_EVM#dhcp
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Retry count exceeded; starting again
link up on port 0, speed 100, full duplex

command 2:

TI8148_EVM#ping 192.168.1.23
link up on port 0, speed 100, full duplex
*** ERROR: `ipaddr' not set
ping failed; host 192.168.1.23 is not alive

Sudheer,

Could you provide me full console log from the u-boot?

What is the external ethernet PHY you are using?

Are you aligned with the below wiki page?

http://processors.wiki.ti.com/index.php/TI81xx_PSP_Porting_Guide#Ethernet_Driver_-_Adding_Custom_Ethernet_Phy

BR
Pavel

 We are using KSZ9031RNX PHY and it has the driver in Linux kernel so we have enabled the driver.

sudheer singh1 said:

We are using KSZ9031RNX PHY and it has the driver in Linux kernel so we have enabled the driver.

What about the u-boot? Can you provide me console output when you try to ping?

BR
Pavel

TI8148_EVM#setenv autoload no

TI8148_EVM#dhcp
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Retry count exceeded; starting again
link up on port 0, speed 100, full duplex

command 2:

TI8148_EVM#ping 192.168.1.23
link up on port 0, speed 100, full duplex
*** ERROR: `ipaddr' not set
ping failed; host 192.168.1.23 is not alive

Sudheer,

sudheer singh1 said:

TI8148_EVM#ping 192.168.1.23
link up on port 0, speed 100, full duplex
*** ERROR: `ipaddr' not set
ping failed; host 192.168.1.23 is not alive

Can you try setting ipaddr? See how below:

TI8148_EVM#ping 172.20.2.57
link up on port 0, speed 100, full duplex
*** ERROR: `ipaddr' not set
ping failed; host 172.20.2.57 is not alive
TI8148_EVM#setenv ipaddr 172.20.2.58
TI8148_EVM#ping 172.20.2.57
link up on port 0, speed 100, full duplex
Using cpsw device
host 172.20.2.57 is alive

Regards,
Pavel

tried but no use

Hit any key to stop autoboot:  0
TI8148_EVM#
TI8148_EVM#setenv autoload no
TI8148_EVM#setenv ipaddr 192.168.1.88
TI8148_EVM#ping 192.168.1.23
link up on port 0, speed 100, full duplex
Using cpsw device
ping failed; host 192.168.1.23 is not alive
TI8148_EVM#ping 192.168.1.17
link up on port 0, speed 100, full duplex
Using cpsw device
ping failed; host 192.168.1.17 is not alive

Sudheer,

sudheer singh1 said:

TI8148_EVM#ping 192.168.1.23

Is 192.168.1.23 the ipaddr of your host/desktop PC?

BR
Pavel

yes

Sudheer,

psp 04.01.00.07 is very old software. What I recommend you is to apply all the u-boot patches related to EMAC/ethernet/net/cpsw from the ti81xx-master branch on top of your u-boot and try again.

http://arago-project.org/git/projects/u-boot-omap3.git?p=projects/u-boot-omap3.git;a=shortlog;h=refs/heads/ti81xx-master

BR
Pavel

Sudheer,

One more question, are you connecting your DM814x board with the host PC directly, or you have switch/hub/router between the dm814x board and the host PC?

BR
Pavel

Pavel,

                  I have tried with u-boot-04.04.00.02 psp and verified that all the patches are present in this version of psp and Ethernet response is same, not able to ping.

Sudheer,

One more question, are you connecting your DM814x board with the host PC directly, or you have switch/hub/router between the dm814x board and the host PC?

BR
Pavel

Hi pavel,

                    I am using the KSZ9031RNX PHY and I have configured environment variables at u-boot level and read the register 0x01 and its value is 0x796D, in this value one bit [1] == 0 which means Jabber not detected.

My concern is like does it should detect Jabber to make ping work.

Sudheer,

sudheer singh1 said:

My concern is like does it should detect Jabber to make ping work.

No, I do not think you need Jabber detected to make ping work.

sudheer singh1 said:

  I am using the KSZ9031RNX PHY

See the below e2e thread, might be in help:

http://e2e.ti.com/support/arm/sitara_arm/f/791/t/247923.aspx

Best Regards,
Pavel

Hi Pavel,

I am using 14.04 on my host.

I am using  VAR-SOM-AM33 device that is based on TI AM335x as target.

I also try to boot the board via TFTP.

I made the same thing that you write in the comment above:

ping 192.168.147.136                                                    

link up on port 0, speed 100, full duplex                                      

link up on port 1, speed 100, full duplex                                      

*** ERROR: `ipaddr' not set                                                    

ping failed; host 192.168.147.136 is not alive                                  

U-Boot# setenv ipaddr 192.168.147.136                                          

U-Boot# ping 192.168.147.136                                                    

link up on port 0, speed 100, full duplex                                      

link up on port 1, speed 100, full duplex                                      

Using cpsw device                                                              

ping failed; host 192.168.147.136 is not alive      

It seems that nothing is going out or in from the Ethernet interface.

I am on this problem for 2 days without finding any answers.

Thanks,

Oren.

Hi Oren,

oren zvuluni said:

U-Boot# setenv ipaddr 192.168.147.136                                          

U-Boot# ping 192.168.147.136      

You are using the same ip addr for host (Ubuntu 14) and target (AM335x board). This is not acceptable.

Can you provide me the output of the below command, run in on host:

host$ ifconfig

Can you also try with addr 192.168.147.130 instead of 192.168.147.136?

U-Boot# setenv ipaddr 192.168.147.130                                         

U-Boot# ping 192.168.147.136  

Regards,
Pavel

"Internal Delay" may be the cause. Please see

     e2e.ti.com/.../169742

To disable "Internal Delay" in the u-boot

   File: uboot/ti/ti8148/evm.c

     /*program GMII_SEL register for RGMII mode */
    //__raw_writel(0x30a, GMII_SEL); // enable internal delay
    __raw_writel(0x33a, GMII_SEL); // disable internal delay

Pavel,

Thanks for the responses here.

device ifconfig output:

root@varsomam33:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 68:9E:19:58:53:A9  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6a9e:19ff:fe58:53a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:648 (648.0 B)
          Interrupt:177

eth1      Link encap:Ethernet  HWaddr 68:9E:19:58:53:AB  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1                              
          RX packets:127 errors:0 dropped:0 overruns:0 frame:0                  
          TX packets:127 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:0                                             
          RX bytes:208737 (203.8 KiB)  TX bytes:208737 (203.8 KiB)  

Host ifconfig output:

oren@oren-Inspiron-3542:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 74:e6:e2:23:22:24  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::76e6:e2ff:fe23:2224/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:63286 (63.2 KB)  TX bytes:11492 (11.4 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:3450 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3450 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:508607 (508.6 KB)  TX bytes:508607 (508.6 KB)

wlan0     Link encap:Ethernet  HWaddr 4c:bb:58:37:48:24  
          inet addr:10.0.0.112  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::4ebb:58ff:fe37:4824/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18303 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19312 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11344575 (11.3 MB)  TX bytes:5670416 (5.6 MB)

I tried this sequence also:

U-Boot # setenv ipaddr 192.168.1.2
U-Boot # setenv serverip 192.168.1.1
U-Boot # setenv gatewayip 192.168.1.1
U-Boot # setenv netmask 255.255.255.0

U-Boot# ping 192.168.1.1
link up on port 0, speed 100, full duplex
link up on port 1, speed 100, full duplex
Using cpsw device
ping failed; host 192.168.1.1 is not alive

The device connected directly to the PC.

I tried to search for the GMII_SEL  that in the next reply but there is no text like that in my U-Boot suorce files.

I think that the problem in my case is that i have two link up, The device connected to only one ETH interface and i get two link up.

Maybe its connected to that.

In DHCP mode it's the same, the device is not getting IP address from the server.

The DHCP server is fine and working, When i am not in U-boot terminal i can configure my device to get an IP address from the DHCP server.

Please help me.

Thanks,

Oren

eth0 is connected.
How can i now what is my TI SDK? The kernel version can tell what i am using? I Downloaded the SW from arago-project site.

How can i know what is the version?

Thanks.