• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 500 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SK-TDA4VM: Ethernet eth0: Link is Down

Gary Wu
Expert 3313 points
Part Number: SK-TDA4VM

Hi ,

  One SK-TDA4VM has ethernet issue as below shown. Is there any test tool for it to check if PHY or else HW is OK? Thanks.

root@j7-evm:/opt/edge_ai_apps# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1
ether 24:76:25:96:22:1b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 82 bytes 6220 (6.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 82 bytes 6220 (6.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@j7-evm:/opt/edge_ai_apps# dhcp
-sh: dhcp: command not found
root@j7-evm:/opt/edge_ai_apps# ifconfig eth0 up
root@j7-evm:/opt/edge_ai_apps# ifconfig eth0 down
root@j7-evm:/opt/edge_ai_apps# ifconfig eth0 up
[ 67.355954] TI DP83867 46000f00.mdio:00: attached PHY driver [TI DP83867] (mi i_bus:phy_addr=46000f00.mdio:00, irq=POLL)
root@j7-evm:/opt/edge_ai_apps# [ 67.370567] am65-cpsw-nuss 46000000.ethernet e th0: Link is Down

  • 0
    TI__Mastermind 23125 points

    Gary, 

    can you confirm if you have tried to set static IP for eth0? sometimes the issue is due to dhcp server. 

    jian

  • 0 in reply to jian35385
    TI__Expert 3313 points

    Hi Jian,

       Thanks for your reply.

    In the same environment, another SK-TDA4VM works and can get IP for ETH0. 

    So I think there is something wrong with this board.  And want to debug where the issue is located.

  • +1 in reply to Gary Wu
    TI__Mastermind 23125 points

    Gary, 

    you can use ethtool -S <if> to query information about driver and MAC. 

    then you can use mdio-tool to read external PHY registers. ethtool is already in the filesystem. you can get mdio-tool from:

    https://github.com/PieVo/mdio-tool

    I think some basic testing such as:

    • static ip
    • direct connection between problem board and a pc, no switch, no router 

    can help us to eliminate other factors.

    A common error that I used to run into is having multiple boards with the same MAC address on the same subnet. but I trust you don't have such issues. 
    Jian