Linux/AM4378: Ethernet ping issue

user284328

Part Number: AM4378
Other Parts Discussed in Thread: AM4372

Tool/software: Linux

Hi,

I am new to the forums, So do apologize if this is a repeat.

We have a custom board which was developed of am437x-gp-evm. We are facing an issue with the Ethernet, when I plug eth1 and eth0 both with saperate subnet, I am able to ping the IP address successfully. The moment eth1 is unplugged ping stops to eth0 too.

Following is the configuration in my dts file:

AM4372_IOPAD(0x910, PIN_INPUT | MUX_MODE1) /* mii1_rxer */
AM4372_IOPAD(0x90C, PIN_INPUT | MUX_MODE1) /* mii1_crs */
AM4372_IOPAD(0x944, PIN_INPUT | MUX_MODE0) /* rmii1_refclk */
AM4372_IOPAD(0x914, PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* mii1_txen.rgmii1_txen */
AM4372_IOPAD(0x924, PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* mii1_txd1.rgmii1_txd1 */
AM4372_IOPAD(0x928, PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* mii1_txd0.rgmii1_txd0 */
AM4372_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_rxd1.rgmii1_rxd1 */
AM4372_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_rxd0.rgmii1_rxd0 */

/* Slave 2 */
AM4372_IOPAD(0x858, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a6.rgmii2_tclk */
AM4372_IOPAD(0x840, PIN_OUTPUT | MUX_MODE2) /* gpmc_a0.rgmii2_tctl */
AM4372_IOPAD(0x854, PIN_OUTPUT | MUX_MODE2) /* gpmc_a5.rgmii2_td0 */
AM4372_IOPAD(0x850, PIN_OUTPUT | MUX_MODE2) /* gpmc_a4.rgmii2_td1 */
AM4372_IOPAD(0x84c, PIN_OUTPUT | MUX_MODE2) /* gpmc_a3.rgmii2_td2 */
AM4372_IOPAD(0x848, PIN_OUTPUT | MUX_MODE2) /* gpmc_a2.rgmii2_td3 */

AM4372_IOPAD(0x85c, PIN_INPUT | MUX_MODE2) /* gpmc_a7.rgmii2_rclk */
AM4372_IOPAD(0x844, PIN_INPUT | MUX_MODE2) /* gpmc_a1.rgmii2_rtcl */
AM4372_IOPAD(0x86c, PIN_INPUT | MUX_MODE2) /* gpmc_a11.rgmii2_rd0 */
AM4372_IOPAD(0x868, PIN_INPUT | MUX_MODE2) /* gpmc_a10.rgmii2_rd1 */
AM4372_IOPAD(0x864, PIN_INPUT | MUX_MODE2) /* gpmc_a9.rgmii2_rd2 */
AM4372_IOPAD(0x860, PIN_INPUT | MUX_MODE2) /* gpmc_a8.rgmii2_rd3 */

&mac {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&cpsw_default>;
pinctrl-1 = <&cpsw_sleep>;
dual_emac=<1>;
status = "okay";
};

&davinci_mdio {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&davinci_mdio_default>;
pinctrl-1 = <&davinci_mdio_sleep>;
status = "okay";
};

&cpsw_emac0 {
phy_id = <&davinci_mdio>,<0>;
phy-mode = "rmii";
dual_emac_res_vlan = <1>;
};

&cpsw_emac1 {
phy_id = <&davinci_mdio>,<5>;
phy-mode = "rgmii";
dual_emac_res_vlan = <2>;
};

Linux Kernel Version: Linux version 4.14.79

Kernel log of PHY:

[ 1.206803] libphy: Fixed MDIO Bus: probed
[ 1.283487] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus freq 1000000
[ 1.291188] davinci_mdio 4a101000.mdio: detected phy mask ffffffde
[ 1.299354] libphy: 4a101000.mdio: probed
[ 1.303400] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 1.312669] davinci_mdio 4a101000.mdio: phy[5]: device 4a101000.mdio:05, driver Micrel KSZ9031 Gigabit PHY
[ 1.323288] cpsw 4a100000.ethernet: Detected MACID = f0:b5:d1:54:be:a0
[ 1.330122] cpsw 4a100000.ethernet: initialized cpsw ale version 1.4
[ 1.336565] cpsw 4a100000.ethernet: ALE Table size 1024
[ 1.341859] cpsw 4a100000.ethernet: cpts: overflow check period 500 (jiffies)
[ 1.349724] cpsw 4a100000.ethernet: cpsw: Detected MACID = f0:b5:d1:54:be:a2

ifconfig -a output:

eth0 Link encap:Ethernet HWaddr F0:B5:D1:54:BE:A0
inet addr:10.74.127.251 Bcast:10.74.127.255 Mask:255.255.255.192
inet6 addr: fe80::f2b5:d1ff:fe54:bea0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128 errors:0 dropped:0 overruns:0 frame:0
TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8420 (8.2 KiB) TX bytes:24020 (23.4 KiB)
Interrupt:51

eth1 Link encap:Ethernet HWaddr F0:B5:D1:54:BE:A2
inet addr:10.74.125.55 Bcast:10.74.125.255 Mask:255.255.254.0
inet6 addr: fe80::f2b5:d1ff:fe54:bea2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10495 errors:0 dropped:54 overruns:0 frame:0
TX packets:651 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1070755 (1.0 MiB) TX bytes:61738 (60.2 KiB)

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:320 errors:0 dropped:0 overruns:0 frame:0
TX packets:320 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23680 (23.1 KiB) TX bytes:23680 (23.1 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)

Settings for eth0:

Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/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
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes

Settings for eth1:

Supported ports: [ TP MII ]
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: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 5
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes

I read the http://processors.wiki.ti.com/index.php/Linux_Core_CPSW_User's_Guide#Dual_Standalone_EMAC_mode but still was not able to come to a conclusion. We want to have the both Ethernet ports eth0 and eth1 work independent of each other. Unpluging eth1 should not effect eth0.

Thank you for your response.

over 5 years ago

0 Bhaskar Reddy over 5 years ago

Intellectual 960 points

Our observation is similar to what's described in this post.

https://e2e.ti.com/support/processors/f/791/t/423910?AM335x-dual-ethernet-problem-in-same-subnet

Setup: Both ethernet address in different subnet

During testing it is observed that when my both ethernet ip address (i.e. eth0=192.168.100.122 and eth1=192.168.2.116) are in different subnet and connected in ethernet switch, both eth ip are pinging.

Case1: when i remove eth0 cable from switch but eth1 cable is inserted , both the ethernet ip addresses stop pinging. Ideally, only eth0 should stop pinging insteed of both stopping.

Case 2: When i remove eth1 cable cable from switch and eth0 cable is already inserted, eth0 is pinging and eth1 is stopped which is proper.

We need to have these two ethernet ports work independently. One port will be connected to office WAN and other port for local LAN connection (for other downstream device communication).

0 Schuyler Patton over 5 years ago in reply to Bhaskar Reddy

TI__Mastermind 36575 points

Hi,

Thanks for posting the reference link. Is your topology the same as the link which if I read correctly has both ports with different subnet addresses connected to the same switch? Could you please attach a diagram of the network topology that you are trying to do? How are the IP addresses being assigned? Please include where the DHCP server capability as well in the network diagram.

Best Regards,

Schuyler

0 Bhaskar Reddy over 5 years ago in reply to Schuyler Patton

Intellectual 960 points

Hi Schuyler,

We tried different network configurations.

With our DTS file, we are getting eth0 (rmii) and eth1 (rgmii) as described in original post.

Test 1,

Connected eth1 in our office LAN. (its getting IP address 10.140.168.90). I can ping from other machine in office LAN. This is fine.
Connected eth0 to a sperate WiFi router (which is not connected to any other upstream network). It's not getting any IP address though the router can assign IP address in 192.168.1.x series.
Assigned 192.168.1.22 statically. I can't ping 192.168.1.1 (router's IP). Connected a laptop to the router which got 192.168.1.2, laptop can ping router IP, 192.168.1.1 but can't ping our board 192.168.1.22

Test 2:

1. Connected eth1 to wifi router. It got IP address 192.168.1.4 and subnet is default 255.255.255.0. It can ping the router and laptop connected to router(192.168.1.2)

2. Connected eth0 to wifi router. It didn't get any ip address. Set 192.168.1.22 manually with subnet as 255.255.254.0

3. Laptop gets response to ping both eth0 and eth1 .

4. Disconnected eth0 : Laptop see's no response from eth0 and eth1 continues to respond.

5. Connected eth0 back: both ping fine.

6. Disconnect eth1: Laptop looses ping response from both eth0 and eth1.

7. Connect eth1: both eth0 and eth1 start responding.

0 Schuyler Patton over 5 years ago in reply to Bhaskar Reddy

TI__Mastermind 36575 points

Hi,

Something I see I want to pursue first before looking at the issue that you are experiencing. Why is eth0 on your board not able to get an ip address and the laptop is? Is the laptop connecting via wireless?

Is ethtool eth0 showing a link detected when connected to the router? If so what is ethool -S eth0 show? Please attach the results to the post.

Best Regards,

Schuyler

0 user284328 over 5 years ago in reply to Schuyler Patton

Prodigy 50 points

Hi Schuyler,

Following are the information that you asked for:

ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/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
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)

Link detected: yes

ethtool -S eth0
NIC statistics:
Good Rx Frames: 6119
Broadcast Rx Frames: 2446
Multicast Rx Frames: 3500
Pause Rx Frames: 0
Rx CRC Errors: 2
Rx Align/Code Errors: 13
Oversize Rx Frames: 0
Rx Jabbers: 0
Undersize (Short) Rx Frames: 0
Rx Fragments: 36
Rx Octets: 884226
Good Tx Frames: 113
Broadcast Tx Frames: 32
Multicast Tx Frames: 24
Pause Tx Frames: 0
Deferred Tx Frames: 0
Collisions: 0
Single Collision Tx Frames: 0
Multiple Collision Tx Frames: 0
Excessive Collisions: 0
Late Collisions: 0
Tx Underrun: 0
Carrier Sense Errors: 0
Tx Octets: 17876
Rx + Tx 64 Octet Frames: 1687
Rx + Tx 65-127 Octet Frames: 1877
Rx + Tx 128-255 Octet Frames: 2185
Rx + Tx 256-511 Octet Frames: 374
Rx + Tx 512-1023 Octet Frames: 123
Rx + Tx 1024-Up Octet Frames: 1
Net Octets: 905512
Rx Start of Frame Overruns: 0
Rx Middle of Frame Overruns: 0
Rx DMA Overruns: 0
Rx DMA chan 0: head_enqueue: 1
Rx DMA chan 0: tail_enqueue: 2641
Rx DMA chan 0: pad_enqueue: 0
Rx DMA chan 0: misqueued: 0
Rx DMA chan 0: desc_alloc_fail: 0
Rx DMA chan 0: pad_alloc_fail: 0
Rx DMA chan 0: runt_receive_buf: 0
Rx DMA chan 0: runt_transmit_bu: 0
Rx DMA chan 0: empty_dequeue: 0
Rx DMA chan 0: busy_dequeue: 2479
Rx DMA chan 0: good_dequeue: 2514
Rx DMA chan 0: requeue: 0
Rx DMA chan 0: teardown_dequeue: 0
Tx DMA chan 0: head_enqueue: 110
Tx DMA chan 0: tail_enqueue: 3
Tx DMA chan 0: pad_enqueue: 0
Tx DMA chan 0: misqueued: 3
Tx DMA chan 0: desc_alloc_fail: 0
Tx DMA chan 0: pad_alloc_fail: 0
Tx DMA chan 0: runt_receive_buf: 0
Tx DMA chan 0: runt_transmit_bu: 7
Tx DMA chan 0: empty_dequeue: 110
Tx DMA chan 0: busy_dequeue: 0
Tx DMA chan 0: good_dequeue: 113
Tx DMA chan 0: requeue: 0
Tx DMA chan 0: teardown_dequeue: 0

0 Schuyler Patton over 5 years ago in reply to user284328

TI__Mastermind 36575 points

Hi,

It looks like the link partner is only capable of connecting at 10Mbps. Is the link partnet a hub? And HW errors are being reported, these need to be tracked down.

Speed: 10Mb/s
Duplex: Full

Rx CRC Errors: 2
Rx Align/Code Errors: 13

Let's verify these are only happening on eth0, please disconnect eth1 and re-run the ethtool and ethtool -S commands. If you have to assign an ip address to get traffic that is ok, we need to make sure which port is seeing the hw errors. Have you modified the file system so that eth0 does not automatically try to obtain an ip address?

Best Regards,

Schuyler

0 user284328 over 5 years ago in reply to Schuyler Patton

Prodigy 50 points

Hey Schuyler,

Thank you your reply.

Following is the link with eth0 is disconnected, I have updated the file system to get the static ip on startup after you said.

ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/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
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes: 10baseT/Half 10baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 10Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000000 (0)

        Link detected: yes

ethtool -S eth0
NIC statistics:
     Good Rx Frames: 184
     Broadcast Rx Frames: 13
     Multicast Rx Frames: 62
     Pause Rx Frames: 0
     Rx CRC Errors: 14
     Rx Align/Code Errors: 24
     Oversize Rx Frames: 0
     Rx Jabbers: 0
     Undersize (Short) Rx Frames: 1
     Rx Fragments: 119
     Rx Octets: 14816
     Good Tx Frames: 127
     Broadcast Tx Frames: 5
     Multicast Tx Frames: 11
     Pause Tx Frames: 0
     Deferred Tx Frames: 0
     Collisions: 0
     Single Collision Tx Frames: 0
     Multiple Collision Tx Frames: 0
     Excessive Collisions: 0
     Late Collisions: 0
     Tx Underrun: 0
     Carrier Sense Errors: 0
     Tx Octets: 11518
     Rx + Tx 64 Octet Frames: 108
     Rx + Tx 65-127 Octet Frames: 235
     Rx + Tx 128-255 Octet Frames: 2
     Rx + Tx 256-511 Octet Frames: 4
     Rx + Tx 512-1023 Octet Frames: 0
     Rx + Tx 1024-Up Octet Frames: 0
     Net Octets: 32992
     Rx Start of Frame Overruns: 0
     Rx Middle of Frame Overruns: 0
     Rx DMA Overruns: 0
     Rx DMA chan 0: head_enqueue: 1
     Rx DMA chan 0: tail_enqueue: 232
     Rx DMA chan 0: pad_enqueue: 0
     Rx DMA chan 0: misqueued: 0
     Rx DMA chan 0: desc_alloc_fail: 0
     Rx DMA chan 0: pad_alloc_fail: 0
     Rx DMA chan 0: runt_receive_buf: 0
     Rx DMA chan 0: runt_transmit_bu: 0
     Rx DMA chan 0: empty_dequeue: 0
     Rx DMA chan 0: busy_dequeue: 105
     Rx DMA chan 0: good_dequeue: 105
     Rx DMA chan 0: requeue: 0
     Rx DMA chan 0: teardown_dequeue: 0
     Tx DMA chan 0: head_enqueue: 126
     Tx DMA chan 0: tail_enqueue: 1
     Tx DMA chan 0: pad_enqueue: 0
     Tx DMA chan 0: misqueued: 1
     Tx DMA chan 0: desc_alloc_fail: 0
     Tx DMA chan 0: pad_alloc_fail: 0
     Tx DMA chan 0: runt_receive_buf: 0
     Tx DMA chan 0: runt_transmit_bu: 36
     Tx DMA chan 0: empty_dequeue: 126
     Tx DMA chan 0: busy_dequeue: 0
     Tx DMA chan 0: good_dequeue: 127
     Tx DMA chan 0: requeue: 0
     Tx DMA chan 0: teardown_dequeue: 0

One point also to note is that with eth1 disconnected on startup I am able to ping eth0 successfully.

0 Schuyler Patton over 5 years ago in reply to user284328

TI__Mastermind 36575 points

Hi,

Thanks for the data, please do not use eth1 at all for the next test.

This error reporting is a concern:

Rx CRC Errors: 14
Rx Align/Code Errors: 24

Can you connect eth0 to another link partner that supports 100Mbps or greater? Also for the next test please remove the static IP configuration for eth0, I would like to see if eth0 can get an IP address on its own.

Best Regards,

Schuyler

0 user284328 over 5 years ago in reply to Schuyler Patton

Prodigy 50 points

Hi Schuyler Patton,

As you said we disconnecte the eth1 cable and connected the eth0 cable only. eth0 cannot get an IP address on its own. Yes I connected the eth1 cable to the eth0 cable so that I was sure a 100 Mbps is used.

Following are the outputs:

ifconfig eth0
eth0      Link encap:Ethernet HWaddr F0:B5:D1:54:BE:A0
          inet6 addr: fe80::f2b5:d1ff:fe54:bea0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:159 errors:0 dropped:1 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15317 (14.9 KiB) TX bytes:2576 (2.5 KiB)
          Interrupt:51

ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/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
        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: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000000 (0)

        Link detected: yes

ethtool -S eth0
NIC statistics:
     Good Rx Frames: 743
     Broadcast Rx Frames: 331
     Multicast Rx Frames: 408
     Pause Rx Frames: 0
     Rx CRC Errors: 57
     Rx Align/Code Errors: 254
     Oversize Rx Frames: 0
     Rx Jabbers: 10
     Undersize (Short) Rx Frames: 0
     Rx Fragments: 14
     Rx Octets: 98019
     Good Tx Frames: 17
     Broadcast Tx Frames: 5
     Multicast Tx Frames: 12
     Pause Tx Frames: 0
     Deferred Tx Frames: 0
     Collisions: 0
     Single Collision Tx Frames: 0
     Multiple Collision Tx Frames: 0
     Excessive Collisions: 0
     Late Collisions: 0
     Tx Underrun: 0
     Carrier Sense Errors: 0
     Tx Octets: 2714
     Rx + Tx 64 Octet Frames: 215
     Rx + Tx 65-127 Octet Frames: 433
     Rx + Tx 128-255 Octet Frames: 259
     Rx + Tx 256-511 Octet Frames: 60
     Rx + Tx 512-1023 Octet Frames: 82
     Rx + Tx 1024-Up Octet Frames: 22
     Net Octets: 227948
     Rx Start of Frame Overruns: 0
     Rx Middle of Frame Overruns: 0
     Rx DMA Overruns: 0
     Rx DMA chan 0: head_enqueue: 1
     Rx DMA chan 0: tail_enqueue: 459
     Rx DMA chan 0: pad_enqueue: 0
     Rx DMA chan 0: misqueued: 0
     Rx DMA chan 0: desc_alloc_fail: 0
     Rx DMA chan 0: pad_alloc_fail: 0
     Rx DMA chan 0: runt_receive_buf: 0
     Rx DMA chan 0: runt_transmit_bu: 0
     Rx DMA chan 0: empty_dequeue: 0
     Rx DMA chan 0: busy_dequeue: 320
     Rx DMA chan 0: good_dequeue: 332
     Rx DMA chan 0: requeue: 0
     Rx DMA chan 0: teardown_dequeue: 0
     Tx DMA chan 0: head_enqueue: 17
     Tx DMA chan 0: tail_enqueue: 0
     Tx DMA chan 0: pad_enqueue: 0
     Tx DMA chan 0: misqueued: 0
     Tx DMA chan 0: desc_alloc_fail: 0
     Tx DMA chan 0: pad_alloc_fail: 0
     Tx DMA chan 0: runt_receive_buf: 0
     Tx DMA chan 0: runt_transmit_bu: 0
     Tx DMA chan 0: empty_dequeue: 17
     Tx DMA chan 0: busy_dequeue: 0
     Tx DMA chan 0: good_dequeue: 17
     Tx DMA chan 0: requeue: 0
     Tx DMA chan 0: teardown_dequeue: 0

Rx CRC Errors: 57
Rx Align/Code Errors: 254

0 Schuyler Patton over 5 years ago in reply to user284328

TI__Mastermind 36575 points

Hi,

Again with eth1 not connected and eth0 connected with the 100Mbps link partner could you please add this node to your DTS file? Please see if eth0 now gets an ip address and please post the results of the ethtool commands.

&phy_sel {

rmii-clock-ext;

};

Best Regards,

Schuyler

0 user284328 over 5 years ago in reply to Schuyler Patton

Prodigy 50 points

Hey Schuyler,

Adding this into the dts file fixed the issue. We are still doing some more test to confirm the fix. Will keep posting.

Processors

Processors forum

Linux/AM4378: Ethernet ping issue