Ehernet interface not up

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ehernet interface not up

1,450 Views
jagadiswar_rao
Contributor I

Hi Team

We are using custom LS2088A board in which, we are using F104S8A Ethernet PHY for QSGMII interface.

We are getting the following error:

getting below  kernel logs.

libphy: Freescale XGMAC MDIO Bus: probed
mdio_bus 8b96000: Error while reading PHY16 reg at 2.2
mdio_bus 8b96000: Error while reading PHY16 reg at 3.3
mdio_bus 8b96000: MDIO device at address 16 is missing.

There is no Ethernet interface is created.

 ifconfig -a
docker0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:cd:a0:f6:7e  txqueuelen 0  (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
        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

sit0: flags=128<NOARP>  mtu 1480
        sit  txqueuelen 1000  (IPv6-in-IPv4)
        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

0 Kudos
1 Reply

1,105 Views
bpe
NXP Employee
NXP Employee

The kernel informs you that it is unable read certain registers in
the PHY and/or the PHY stops responding while being initialized.
This can be a Device Tree or a hardware issue. Suggestions:

1. Make sure you properly specified the PHY connection to the processor
   MDIO and the PHY management addresses in the Device Tree. Take
   fsl-ls1088a-rdb.dts as a reference.
   
2. Monitor MDIO/MDC interface with a scope, make sure the signal shapes
   meet the requirements of the processor and the PHY Hardware
   Specifications.
   
  


Have a great day,
Platon

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos