Hi,
We've designed a custom board based on the OMAP-L138. I'm using the ti-dvsdk_omapl138-evm_04_03_00_06. I have modified the Kernel and Uboot to work with RMII instead of MII as far as I could. The ethernet PHY is a LAN8720.
Now when I boot, this is the result:
---
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=0:00, id=
7c0f1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
net eth0: DaVinci EMAC: ioctl not supported
eth0 no wireless extensions.
udhcpc (v1.13.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
-----
and inside linux when I type ifconfig I get:
eth0 Link encap:Ethernet HWaddr D6:7D:56:5B:5A:9E
UP BROADCAST MULTICAST MTU:1500 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)
Interrupt:33
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:16436 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
This behaviour is the same wether there is an ethernet cat cable plugged in or not.. I also never get any of the ethernet LEDs to blink.
What can be the source of the problem? Bad connector or wrong phy initialization?
Thanks in advance :)
-Koteich
