DP83867CS: not getting detected.

Hi Venkat,

Venkata Rao M said:

1) Does DP83867CS require drivers for detection in UBUNTU OS ?

Yes, PHY driver and proper configuration in DTS/defconfig/makefile/kconfig/.. is required to ensure driver imports and is used to identify the PHY on start-up.

Venkata Rao M said:

2) We are not able to list in ifconfig.

This is likely due to driver not imported correctly. Please refer to this app-note:

https://www.ti.com/lit/an/snla450/snla450.pdf

Do you have any working example with PHY detected in Ubuntu system? If so, I recommend modifying the driver to match the PHY_ID of DP83867. From this, you can confirm if PHY is alive and SMI communication to INTEL I210S is working. If this test case passes, then the original issue is only with properly importing the 867 driver.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/phy/dp83867.c?h=v5.10.237 (run "uname -r" to confirm Linux version - import appropriate version into your system)

Thank you,
Evan

Hi Evan,

Thanks for your prompt response.

Question: Do you have any working example with PHY detected in Ubuntu system?

Ans: No, we are working for the first time on this design.

We have some queries related to hardware :

1) Can you please guide how to do strap configuration for enabling SGMII as an input, what are the signals we need to configure?

2) We are using I210S for providing input for DP83867CS, IS it necessary to connect MDC and MDIO signals of PHY for proper functioning of PHY with SGMII.

Regards,

Venkat.

Regards,

Venkat. 

Hi Venkat,

Venkata Rao M said:

1) Can you please guide how to do strap configuration for enabling SGMII as an input, what are the signals we need to configure?

To enable SGMII:

• LED_0 strapped into Mode 2 or 4 (mode 2 recommended for mirror mode disable, if MDI traces are not crossed in schematic
• RX_CTRL strapped into Mode 3 or 4 (disable internal test mode to avoid unexpected behavior)

Venkata Rao M said:

2) We are using I210S for providing input for DP83867CS, IS it necessary to connect MDC and MDIO signals of PHY for proper functioning of PHY with SGMII.

It is not required, but highly recommended for debug purposes. Configuring the PHY for MDI link and SGMII enable can be done through straps alone. In the event of any error, it will be challenging to debug without register access through SMI.

Thank you,
Evan 

Hi Evan,

That was very informative, We have done the above strap configuration but we are facing below issues:

1)The link is not being established. Images attached FYR(Image1- enp3S0 is port related to DP83867CS).

2) As per the app note suggested by you The below command doesn't throw any messages in terminal;

    dmesg | grep -i mdio

   But as per the app note, it should throw some error or should display the drivers linked. Image attached FYR (Image2).

3) The port is being listed in ifconfig but not able to link. Image3 attached FYR.

4) Does the Image4 mean something, For your information.

Note: Pictures are named for better reference.

Thanks & Regards,

Venkat.

Hi Venkat,

It seems the driver is compiled in your system, but not being loaded on start-up. 

"dmesg | grep -i mdio" is expected to show some messages relating to PHY probe attempt / detection. Even without PHY alive or driver imported properly, I still expect some MDIO probe attempt when Ethernet is enabled in device tree.

Do you have Ethernet enabled in your device tree, kconfig, makefile, defconfig, ... ? Please review the driver integration appnote shared in my earlier reply and let me know any gaps in the steps relative to your system.

Thank you,
Evan

Hi Evan,

I have checked in source code of ubuntu 20.04 which has linux kernel version 5.15.0-159 generic where i can see dp83867.c driver already present in it. And also enabled as module in make menu config.but still if i do dmesg | grep mdio i cannot get anything.Can you please help me out in this. If i am missing any steps can you please guide me step by step.

I have attached my schematics FYR, Can you please check and let me know any discrepancies found?

Thanks in advance.

 Regards,

Venkat.

Hi Venkat,

I don't see any concerns in the schematic that would cause this issue.

Could you please share your device tree and SoC part number?

I'm looking for device tree file with Ethernet entries similar to this:

Thank you,
Evan

Hi Evan,

We dont find any device tree same as above in our source code. Only i can find the below listed files under arch/arm64/boot/dts/ti

k3-am642.dtsi     k3-am6528-iot2050-basic.dts   k3-am65-iot2050-common.dtsi     

k3-j7200-main.dtsi     k3-j721e-mcu-wakeup.dtsi

k3-am642-evm.dts      k3-am6548-iot2050-advanced.dts    k3-am65-main.dtsi 

k3-j7200-mcu-wakeup.dtsi    k3-j721e-som-p0.dtsi

k3-am642-sk.dts    k3-am654-base-board.dts     k3-am65-mcu.dtsi   k3-j7200-som-p0.dtsi      

     
k3-am64.dtsi       k3-am654.dtsi    k3-am65-wakeup.dtsi   k3-j721e-common-proc-board.dts

k3-am64-main.dtsi  k3-am654-industrial-thermal.dtsi  k3-j7200-common-proc-board.dts

k3-am64-mcu.dtsi   k3-am65.dtsi   k3-j7200.dtsi  k3-j721e-main.dtsi    k3-j721e.dtsi

2)Part number for SOC: NANOCOM-TGUST-A10-CS-TI-01

3) I have a query related to connections of SGMII : Does The SGMII connections between The I210IS and DP83867CS has to be crossed ??

i.e.

SGMII output of I210IS to SGMII input of DP83867CS..?? or it has to connected straight.

Regards,

Venkat.

Hi Venkat,

We don't have experience with enabling Ethernet for non-TI SoC - this will require support from Intel.

I recommend finding an Ubuntu Intel platform with Ethernet enabled, so there is a reference file-set to work from to understand missing configs.

After confirming Ethernet is enabled and MDIO bus is being probed, I can help debug any PHY-related software or hardware issues. 

Venkata Rao M said:

3) I have a query related to connections of SGMII : Does The SGMII connections between The I210IS and DP83867CS has to be crossed ??

PHY(SGMII_SIP/N) connected to I210IS SGMII output.

PHY(SGMII_SOP/N) connected to I210IS SGMII input.

Thank you,
Evan