AM4376: Issue with Ethernet Configuration on Custom AM4376 Board

Part Number: AM4376

Tool/software:

Hello TI Support Team,

We are working with two custom AM4376 boards, both using the same software and hardware configuration. Each board has 512MB NAND and 500MB DDR. The first board is working fine with Ethernet, where the Transceiver is detected as "external" and the connection is established without any issues.


Board 1:
        Ethernet works fine.
        ethtool reports the transceiver as external.

Log (Board 1):

Transceiver: external
Link detected: yes



However, on the second board, we are encountering a problem. The Transceiver is detected as "internal," and the Ethernet is not coming up. Both boards use separate SoC to PHY connections, and the PHY is external on both. Despite this, the second board is not behaving as expected.


Log (Board 2):

    Transceiver: internal
    Link detected: yes
    

Could you provide guidance on:

    Why Board 2 detects the transceiver as internal instead of external?
    Possible steps to debug or resolve this issue.
    Any specific configuration or software adjustments required for PHY detection in this case.
        
Thank you!

Best regards

Both board logs

============



Board 1 log   //working
============
root@am437x-evm:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP    MII ]
        Supported link modes:   100baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  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: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: external                   
        MDI-X: Unknown
        Link detected: yes




Board 2 log    //Not working
=============

root@am437x-evm:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 90:06:F2:B6:C4:32  
          inet6 addr: fe80::9206:f2ff:feb6:c432/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:11264 (11.0 KiB)

eth1      Link encap:Ethernet  HWaddr F6:45:D9:61:F5:46  
          inet6 addr: fe80::f445:d9ff:fe61:f546/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:22170 (21.6 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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:140 (140.0 B)  TX bytes:140 (140.0 B)

root@am437x-evm:~#

root@am437x-evm:~#
root@am437x-evm:~#
root@am437x-evm:~#
root@am437x-evm:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   100baseT/Full
        Supported pause frame [  460.017519] Karthi phy_ethtool_ksettings_get 266
use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: [  460.017560] Abinash 0
Not reported
        Advertised link modes:  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: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Link detected: yes
root@am437x-evm:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   100base[  463.819106] Karthi phy_ethtool_ksettings_get 266
T/Full
        Supported pause frame use: No
        Supports auto-negotiat[  463.819148] Abinash 0
ion: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  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: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Link detected: yes
          

  • Hi,

    I am currently out of the office and will be returning the second week of January.

    The ethtool response here is returning what is read out of the PHY. What PHY is being used here?

    What does ethtool -S return for each interface?

    Best Regards,

    Schuyler