• State Suggested Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 533 subscribers
  • Views 5504 views
  • Users 0 members are here
Options
Related

Using KSZ9131 on RZG2H Board and kernel 5.10.138 LTS-SDK3.0.3

Linux kernel programming

Hi Forum,

We have a customized  rzg2h Board (taken a reference of rzg2h-hihope board, In the new custom board we replaced realtek with  ksz9131RNX.

We used the same pin connection in the hardware and in the kernel config we disabled the realtek and enabled ksz9131 but the phy is non functional.

And we not able to probe and detect the phy.

Could any one here  help/point  us  to the steps required to get this phy up .

Thanks and regards,

Nagaraja

  • 0 in reply to MicBis

    Hi MicBis,

    Basically we have two custom board one based on RZG2N and another based on RZG2H ,taken a reference of hi-hope evaluation board.

    We are using SDK-1.0.6( Kernel 4.19.)  for RZG2N custom board  where ksz9131 is working fine no packet loss, ethernet is workig fine. we are able to stream 16 IP cameras using gstreammer.

    We are using sdk-3.0.3 for rzg2h custom board  beause we need to interface da7218 also. Using this playback is working fine and capture is having issue.The kernel we are using  is 5.10.138. in This case ksz9131 is not working we encounter a 50-80 % packet loss.

    The below dts configuration  used in sdk-1.0.6  and is wokring fine

    &avb {
            status = "okay";
             pinctrl-names = "default";
             phy-handle = <&phy1>;
            phy-mode = "rgmii-id";
           phy1: phy@3 {
                    reg = <0x3>;
                    compatible = "ethernet-phy-ieee802.3-c22";
           };
    };

    Tried modifying the dts configration as mensioned in my earlier mail but no improvement.

    But the same configuration is giving 50-80 packet loss in sdk-3.0.3

    Could you please tell us what is the changes required to get ksz9131 on SDK-3.0.3.

    Thanks and regards,

    Nagaraja

  • 0 in reply to Linux kernel programming

    Hi,

    In this situation, the PHY and MAC are communicating successfully,
    and I don't think the PHY and packet loss issue are related.

    Can you determine whether packet loss is occurring on transmit, receive, or both?
    Also, if you look at it over a slightly longer period of time, does packet loss continue to occur?
    Or does packet loss happen suddenly and then recover repeatedly?

    What are the error statistics displayed by ifconfig after communication?
    Are there any ethernet driver errors output in the kernel log displayed by dmesg?

    How is it?

    BR