This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83869HM: Need to confirm how can I create a phy node with bridge node as dp83869

Part Number: DP83869HM
Other Parts Discussed in Thread: DP83869

Tool/software:

 

As mentioned in the earlier thread, the DP83869 depends on the link status of the downstream PHY. In my case, the downstream PHY is the ADIN1100. Could you please advise how I can bring its link status up?

J784S4XEVM: Need Explanation in the SGMII-RGMII mode

I have:

Added the necessary nodes in the DTS.

Configured the hardware according to the strap pins.

Verified that the DP83869 is set to SGMII–RGMII bridge mode through registers.

However, the link is still not coming up. Could you help me with debugging this issue?

Regards,
Kowshika

  • Hi Kowshika, 

    Please try adding a fixed-link configuration on the DTS to set the link permanently high on DP83869 and see if that gets the link up. 

    Best,
    J

  • I gave the below dts node and got the below output.

    &main_cpsw0_mdio {
    status = "okay";
    pinctrl-names = "default";
    pinctrl-0 = <&main_cpsw9x1_mdio_pins_default>;
    pinctrl-1 = <&main_pmx_gpio_vddshv20_pins_default>; // Keep if needed for your board

    /* ADIN1100 - Connected via RGMII to DP83869 bridge */
    adin1100: ethernet-phy@0 {
    reg = <0>; // ADIN1100 behind DP83869
    // Note: This may still be needed for downstream config, but not for CPSW link
    };

    /* DP83869 Bridge PHY - Connected to CPSW SGMII port */
    bridge_phy: ethernet-phy@3 {
    reg = <3>; // DP83869 address
    // Optional: Add compatible = "ti,dp83869" if driver requires it
    };
    };

    &main_cpsw0_port5 {
    status = "okay";
    phy-mode = "sgmii"; // Keep SGMII as per your setup
    // phy-handle = <&bridge_phy>; // Comment out or remove to use fixed-link
    phys = <&cpsw0_phy_gmii_sel 5>, <&serdes2_sgmii_link>;
    phy-names = "mac", "serdes";

    fixed-link {
    speed = <1000>; // 1 Gbps, as "permanently high" implies Gigabit
    full-duplex; // Full-duplex mode
    pause; // Optional: Enable flow control (omit if not needed)
    };
    };





    Can you explain what this illustrates?

  • Hi,

    It looks like the PHY is linking up. Can you verify if it can receive packets? It looks like it can send packets out.

    Best,

    J

  • How can I test that?

    Could you please provide me the steps?


    Regards,
    Kowshika

  • Hi Kowshika, 

    Can you try ping or iperf?
    Best,
    J

  • Already tried the same it was able to ping the same ip address not the other addresses in the same subnet.

    What does that mean?

    Regards,
    Kowshika

  • Hi Kowshika, 

    If there is no route to the gateway, then the ping may not work. Is the default route set in Linux?

    Best,
    J



  • When i was trying to add a default route,this is the issue i faced.

    Regards,
    Kowshika

  • Hi Kowshika, 

    I understand the ping doesn't work and default route cannot be set. 
    I am wondering if Linux is detecting a fake link. 
    Is there any other logs that come out for this port?

    Best,
    J

  • root@j784s4-evm:/opt/edgeai-gst-apps# dmesg | grep cpsw
    [ 1.347180] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA02102, cpsw version 0x6BA82102 Ports: 2 quirks:00000000
    [ 1.360040] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
    [ 1.367247] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
    [ 1.377563] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010b, freq:500000000, add_val:1 pps:1
    [ 1.463605] am65-cpsw-nuss c000000.ethernet: initializing am65 cpsw nuss version 0x6BA03102, cpsw version 0x6BA82902 Ports: 9 quirks:00000000
    [ 1.887190] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA02102, cpsw version 0x6BA82102 Ports: 2 quirks:00000000
    [ 1.900059] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
    [ 1.907266] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
    [ 1.917605] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010b, freq:500000000, add_val:1 pps:1
    [ 1.927699] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
    [ 2.011433] am65-cpsw-nuss c000000.ethernet: initializing am65 cpsw nuss version 0x6BA03102, cpsw version 0x6BA82902 Ports: 9 quirks:00000000
    [ 2.025292] am65-cpsw-nuss c000000.ethernet: Use random MAC address
    [ 2.031556] am65-cpsw-nuss c000000.ethernet: initialized cpsw ale version 1.5
    [ 2.038677] am65-cpsw-nuss c000000.ethernet: ALE Table size 512
    [ 2.044936] am65-cpsw-nuss c000000.ethernet: CPTS ver 0x4e8a010c, freq:250000000, add_val:3 pps:0
    [ 2.056288] am65-cpsw-nuss c000000.ethernet: set new flow-id-base 82
    [ 7.073440] am65-cpsw-nuss c000000.ethernet eth1: PHY [c000f00.mdio:03] driver [TI DP83869] (irq=POLL)
    [ 7.082750] am65-cpsw-nuss c000000.ethernet eth1: configuring for inband/sgmii link mode

    This is one of the logs which i got from the port.

    Regards,
    Kowshika

  • Hi Kowshika, 

    Is there any log after the inband/sgmii link mode configuration? If not, it seems like linux never gets out of configuration stage. 

    Best,
    J