• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 188 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5718: Ethernet issue

bhardwaj kotha
Intellectual 270 points
Part Number: AM5718

Hi,

We are using Marvell 88E1512 PHY connected to Sitara AM5718. Booted the board  and an ip is set to the eth1, then checked for settings for eth1 by giving the command ethtool eth1. The settings are given below. We have verified that tx and rx clks are coming(25Mhz) and at test point 3 we are getting 125Mhz clk.

Supported ports: [ TP MII FIBRE ]                                       
        Supported link modes:   10baseT/Half 10baseT/Full                       
                                100baseT/Half 100baseT/Full                     
                                1000baseT/Half 1000baseT/Full                   
        Supported pause frame use: Symmetric Receive-only                       
        Supports auto-negotiation: Yes                                          
        Supported FEC modes: Not reported                                       
        Advertised link modes:  10baseT/Half 10baseT/Full                       
                                100baseT/Half 100baseT/Full                     
                                1000baseT/Half 1000baseT/Full                   
        Advertised pause frame use: No                                          
        Advertised auto-negotiation: Yes                                        
        Advertised FEC modes: Not reported                                      
        Link partner advertised link modes:  10baseT/Half 10baseT/Full          
                                             100baseT/Half 100baseT/Full        
        Link partner advertised pause frame use: Symmetric Receive-only         
        Link partner advertised auto-negotiation: Yes                           
        Link partner advertised FEC modes: Not reported                         
        Speed: 100Mb/s                                                          
        Duplex: Full                                                            
        Port: MII                                                               
        PHYAD: 1                                                                
        Transceiver: internal                                                   
        Auto-negotiation: on                                                    
        Supports Wake-on: g                                                     
        Wake-on: d                                                              
        Current message level: 0x00000000 (0)

                                                                               
        Link detected: yes

After that we tried to ping but it is not working

root@am57xx-evm:~# ping 192.168.7.25                                            
PING 192.168.7.25 (192.168.7.25): 56 data bytes                                 
.^C                                                                             
--- 192.168.7.25 ping statistics ---                                            
15 packets transmitted, 0 packets received, 100% packet loss

I have another problem that we are given the connections for eth0 but the phy is detected on eth1.

cpsw 48484000.ethernet eth1: Link is Up - 100Mbps/Full - flow con
trol rx/tx                                                                      
[   23.062041] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Please answer as soon as possible.

Thanks & regards,

Bhardwaj

  • 0
    TI__Mastermind 38980 points

    Hi Bhardwaj,

    bhardwaj kotha said:
    I have another problem that we are given the connections for eth0 but the phy is detected on eth1.

    How have you given the connections to eth0? Can you please elaborate.

    Can you please answer the following questions :

    • What is the MAC protocol used? RGMII/RMII?
    • What are the delay settings of the Phy?
    • Can you try to do a Phy loopback test and MAC loopback test to see if Phy is sending the Packets or not.

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    Intellectual 270 points

    hi,

    How have you given the connections to eth0? Can you please elaborate.

    yes, it is given to eth0.

    In our schmatics we have four tx(u6,v6,u7,v7) and four rx pins(w2,y2,v3,v4) coming from sitara and given to marvell 88E1512 phy IC , ctrl pins (txctl(v9),rxctl(v5) ) ,clk pins( rxclk(u5),txclk(w9) )

     mdio_clk(u4),mdio_data(v1) are given to marvell 88E1512 phy.

    What is the MAC protocol used? RGMII/RMII?

    we are using RGMII.

    I dont have any previous working in this kind of processors which works on linux and on ethernet.

    I haven't change any settings which are there. Can you tell me where should i change if required.

    I observed that while pinging there is no data on tx lines coming out from sitara.

  • 0 in reply to Tanmay Patil
    Intellectual 270 points

    hi,

    can u give me some suggestions, How to solve this problem.

    bhardwaj

  • 0 in reply to Tanmay Patil
    Intellectual 270 points

    Hi, 

    This is our ethernet phy and the connections.

    Thanks & regards

    Bhardwaj 

  • 0 in reply to bhardwaj kotha
    TI__Mastermind 38980 points

    Hi Bhardwaj,

    Sorry for the delay in response.

    Can you share the kernel bootlog which you are getting.

    You can get the statistics of the packets being sent and received using the command "ethtool -S eth1". Can you see if you see any increase in drop frames as ping goes on. Please also check if you see any increase in rx and tx packets in the output of ifconfig command.

    Tanmay Patil said:
    What are the delay settings of the Phy?

    These are usually set in the board design by tweaking the resistors on some pins. Can you please check with your hardware team regarding this.

    Regards,
    Tanmay