AnsweredAssumed Answered

ethtool replying MII

Question asked by Asma Alekar on Sep 5, 2019
Latest reply on Sep 16, 2019 by Yuri Muhin

Hi All,

I am trying to connect ethernet driver with on our custom IMX6UL board with TI PHY DP83822 .

Once booted I get following log(filtered):

 

OK ] Reached target Timers.
[ OK ] Listening on dropbear.socket.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Login Service...
Starting RPC Bind Service...
Starting Network Time Service (one-shot ntpdate mode)...
[ OK ] Started Periodic Command Scheduler.
[ OK ] Started TEE Supplicant.
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started Login Service.
Starting Telephony service...
[ OK ] Started Job spooling tools.
[ OK ] Started Updates psplash to basic.
Starting Avahi mDNS/DNS-SD Stack...
Starting Connection service...
Starting System Logging Service...
[ OK ] Started RPC Bind Service.
[ OK ] Started Network Time Service (one-shot ntpdate mode).
[ OK ] Started System Logging Service.
TI DP83822 10/100 Mbps PHY 20b4000.ethernet-1:01: attached PHY driver [TI DP83822 10/100 Mbps PHY] (mii_bus:phy_addr=20b4000.ethernet-1:01, irq=POLL)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ OK ] Started Telephony service.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Connection service.
Starting Hostname Service...
Starting WPA supplicant...
Starting Kernel Logging Service...
[ OK ] Started WPA supplicant.
[ OK ] Reached target Network.
[ OK ] Started Update psplash to network.
Starting Terminate Psplash Boot Screen...
Starting /etc/rc.local Compatibility...
[ OK ] Started NFS status monitor for NFSv2/3 locking..
[FAILED] Failed to start Terminate Psplash Boot Screen.
See 'systemctl status psplash-quit.service' for details.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started Hostname Service.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttymxc0.
[ OK ] Reached target Login Prompts.
[ OK ] Started Kernel Logging Service.
[ OK ] Reached target Multi-User System.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.

NXP i.MX Release Distro 4.14-sumo imx6ulevk ttymxc0

imx6ulevk login: root

I can see the driver is registered. I have set RMII Phy mode in device tree.

But when I do ethtool eth0, it gives me the following output:

 

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: no

Does it mean my device is not set in RMII mode, because I am not able to ping as well.

It gives me host unreachable?

Outcomes