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.

PROCESSOR-SDK-AM62A: Failed to ping Ethernet on sdk-linux-rt-edgeai-am62a-evm-11.01.07.05

Part Number: PROCESSOR-SDK-AM62A


Tool/software:

TI expert:

We have a project using AM62A with SDK version 9.1, where we have completed the debugging of the Marvell MV88Q2112 PHY driver.

For some reasons, we have now upgraded to the latest 11.01 RTLinux SDK. On the new SDK, the Ethernet cannot be pinged successfully. Please help analyze the possible causes.

The ping command always return "Network is unreachable"

root@am62axx-evm:~# ping 192.168.1.100
ping: connect: Network is unreachable

The ifconfig info 

root@am62axx-evm:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.198  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::625:e8ff:feb1:698c  prefixlen 64  scopeid 0x20<link>
        ether 04:25:e8:b1:69:8c  txqueuelen 1000  (Ethernet)
        RX packets 21  bytes 1260 (1.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9  bytes 726 (726.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        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

The ethtool info

root@am62axx-evm:~# ethtool eth0
Settings for eth0:
        Supported ports: [  ]
        Supported link modes:   100baseT1/Full
                                1000baseT1/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  100baseT1/Full
                                1000baseT1/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: off
        master-slave cfg: forced master
        master-slave status: master
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: external
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x000020f7 (8439)
                               drv probe link ifdown ifup rx_err tx_err hw
        Link detected: yes
        SQI: 15/15

dmesg info

root@am62axx-evm:~# dmesg | grep am65-cpsw-nuss
[    1.702480] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01103, cpsw version 0x6BA81103 Ports: 3 quirks:00000006
[    1.739917] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[    1.739925] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512, Policers 32
[    1.740744] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:1
[    1.781292] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
[    6.971283] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:02] driver [mv88q2112] (irq=POLL)
[    6.971300] am65-cpsw-nuss 8000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
[   10.152251] am65-cpsw-nuss 8000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off

I can capture some ARP packet by  tcpdump  when ping the board from host PC.

root@am62axx-evm:~# tcpdump -i eth0 -v
[ 4762.694189] am65-cpsw-nuss 8000000.ethernet eth0: entered promiscuous mode
[ 4762.694284] audit: type=1700 audit(1748549262.513:4): dev=eth0 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[ 4762.694597] audit: type=1300 audit(1748549262.513:4): arch=c00000b7 syscall=208 success=yes exit=0 a0=4 a1=107 a2=1 a3=ffffd84a0fa0 items=0 ppid=845 pid=3074 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0)
[ 4762.694626] audit: type=1327 audit(1748549262.513:4): proctitle=74637064756D70002D690065746830002D76
tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
20:07:43.031649 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:44.055663 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:46.104761 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:47.128682 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:48.151815 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:50.199762 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:51.224599 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:52.247652 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:53.271986 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:54.295636 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46
20:07:55.319710 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has am62axx-evm tell 192.168.1.100, length 46

  • Hello Chi Chen, 

    Apologies for the delay in response. 

    May I ask how you obtained your IP address? I.e. was it dynamically assigned or statically/manually configured?

    I noticed your netmask is 255.255.255.255, this is problematic because this means your AM62A board and devices connected to it will not be on the same subnet and could be a reason for ping failure.

    -Daolin