DM8168 boot can not find eth1

Hi Xavier,

Did you try with the commands described below ?

http://processors.wiki.ti.com/index.php?title=TI81XX_PSP_Ethernet_Switch_User_Guide#Bringing_Up_interfaces

Best Regards,

Pavel

Hi Pavel,

I am using custom DM8168 processor with vsc8502 dual phy chip for ethernet, my eth0 works fine but eth1 not waking up.

log message is :

dmesg | grep phy
davinci_mdio davinci_mdio.0: detected phy mask ffffff3f
davinci_mdio davinci_mdio.0: phy[6]: device 0:06, driver unknown
davinci_mdio davinci_mdio.0: phy[7]: device 0:07, driver unknown
Emac set phy config 0x3140
Emac set phy config tmp1 0x3140
Emac set phy config tmp2 0x796d
Emac set phy config tmp3 0x1e1
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:06, id=70631)
net eth1: could not connect to phy 0:02

And eth1 does not get connecting at all, what could be the issue, please let me know.

Thanks,

Vidya
 

Vidya,

Vidya Sagar said:

my eth0 works fine but eth1 not waking up

eth1 not working in u-boot or in linux kernel?

Are you using EZSDK or DVR RDK? Which version?

BR
Pavel

See also the below e2e thread:
e2e.ti.com/.../383860

BR
Pavel

Hi Pavel,

Thanks for reply.

I am using EZSDK ezsdk_dm816x-evm_5_05_02_00_setuplinux, and Ethernet in MII mode.

I do not have any issue with one phy its working on u-boot loader as well as linux also but second ethrenet phy does not work.

Please help me to resolve the issue.

Thanks,
Vidya

Hi Vidya,

Can you run the HW diagnostic test (emac_mii_test.c) for eth1? You need first verify that everything is correct from the HW side.

BR
Pavel

Dear Pavel,

Eth1 id we are getting but not getting link on emac_mii_test tool in the CCS, I am trying to enable eth1 and eth0 on kernel level eth0 works fine but eth1 does not work.

On kernel stage also we are getting PHY id but link is not getting up, what is the issue not getting.

If any patch is available for eth1 link please send me, my hardware looks ok because getting the mdio register values on kernel stage.

Please suggest me how to resolve the problem and how my eth1 port will up.

Thanks,

Vidya

Vidya,

Does eth1 work fine in u-boot? Note that you can not use both EMAC ports (eth0 and eth1) in u-boot at the same time.

BR
Pavel

Hi Pavel,

Thanks for reply.

I am getting only one PHY up on u-boot stage, how i can get both port on u-boot.

But one port works fine able to do tftp boot and nfs boot, please tell me what need to do for eth1 on u-boot as well as kernel level.

Thanks,
Vidya

Vidya,

Vidya Sagar said:

I am getting only one PHY up on u-boot stage, how i can get both port on u-boot.

You can not get both ports (eth0 and eth1) in u-boot, as u-boot ethernet does not have TCP/IP stack. Only one port (eth0 or eth1) can be available in u-boot stage.

Regarding linux kernel, there you can have both ports (eth0 and eth1). See the below links for more info:

 

BR
Pavel

Dear Pavel,

We are getting dmesg output on Linux,

dmesg |grep eth
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:06, id=70631)
net eth1: PHY already attached
net eth1: could not connect to phy 0:02
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:06, id=70631)
net eth1: PHY already attached
net eth1: could not connect to phy 0:02

and only eth0 is working.

then if we disable using ifdown command and enable eth1, ping is happening.

Could you please guide me where I am wrong.

 

Thanks,

Vidya

Hi Pavel,

If I do dmesg | grep eth gets like
dmesg |grep eth
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:06, id=70631)
net eth1: PHY already attached
net eth1: could not connect to phy 0:02
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:06, id=70631)
net eth1: PHY already attached
net eth1: could not connect to phy 0:02

mean PHY already attached, then could not connect to phy 0:02
not getting exactly what is the issue.

If I do manual setting ifup eth1 and then ifconfig eth1 <ip> netmask <mask> up
then gets ip address but not able to ping.

If I do ifdown eth0 and then ifup eth1 followed to set ip address, eth1 works fine, but eth0 does not work.

At a time only one port is getting up.

Please guide me how both port will work on the kernel level.

Thanks,
Vidya