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.

Linux/66AK2H12: eth2 & eth3 can not receive packegs

Part Number: 66AK2H12

Tool/software: Linux

Hi

66AK2H12 has for sgmii, form sgmii 1 to sgmii 4.

On my board, 66AK2H12's SGMII 2 and SGMII3 connect to another Soc's two sgmii directly, mac to mac.

66AK2H12 can communicate with the Soc through sgmii 2,but 66AK2H12 cannot receive soc's packet through sgmii 3, I check the gbe_switch's statistic. The switch has received the packets form soc,and ale_table has the correct mac address of the soc。66AK2H12's  transmit is ok,soc can receive 66AK2H12's packets.

66AK2H12's SGMII 4 connect to DP83867.In uboot, it works well, ping and tftp are working properly. But when linux boots up,SGMII4 works like sgmii3,PC can receive packets form 66AK2H12, but 66AK2 can't receive PC's packets.

EVMK2H's dts file support SGMII1 SGMII2, I modifiy the dts file to support SGMII 3 and SGMII 4. SDK is  processor sdk 05.01.00.11

here is the dts file, looking forward to  reply

keystone-k2hk-netcp.7z

  • Hi,

    When all interfaces are connected: 66AK2H12's SGMII2 & SGMII3 connected to the SoC & 66AK2H12's SGMII4 connected to PC, what is the output of: ifconfig?

    Are all SGMII interfaces UP?

    Best Regards,
    Yordan
  • sgmii3 connect to another soc. sgmii links ok.the netdev is eth2,when ping soc ,soc can capture the packets by tcpdump.
    sgmii4 connect to dp83867.sgmii links ok. dp83867 also links up. netdevice is eth3.when ping pc, pc capture packets by wireshark.
    both pc and soc response to the ping cmd.
    the statistic of receive frame are matched to pc and soc's response packets.But, there is no receive interrupts in linux.
    so, I guess, maybe some configurations were wrong, the dma channel or rx_flow?I only modified the dts.
    can you give me some suggestions ...thank you
  • I changed sdk from 05.01.00.11 to 04.03.00.05.

    I only changed the dts file, no change of the linux source code in 04.03.00.05. eth2 & eth3 are working normally.

    So, I think, my dts file used in SDK 5.X maybe NOT correct.
    Do Ti have some examples of dts to use eth2 & eth3 successfully? based on processor SDK 5.x, not 4.x.

    could you please take a look to this issue?

  • Hi,

    Have you configured the correct phys in keystone-k2hk-evm.dts:
    &mdio {
    status = "ok";
    ethphy0: ethernet-phy@0 {
    compatible = "marvell,88E1111", "ethernet-phy-ieee802.3-c22";
    reg = <0>;
    };

    ethphy1: ethernet-phy@1 {
    compatible = "marvell,88E1111", "ethernet-phy-ieee802.3-c22";
    reg = <1>;
    };
    };

    Best Regards,
    Yordan