AM2434: AM2434 Interface to DP83826

Part Number: AM2434
Other Parts Discussed in Thread: DP83869, DP83867E, SYSCONFIG

Hello,AM2434_DP83826.png

We are trying to migrate from DP83869 GBE in Ti Eval board design to DP83826 + HX1188FNLT MBE and use 4 wire M12 cable instead of RJ45 Mag jack. There are 2 questions in this regard

  1. Share a reference design of PHY with M12 /4 Wire termination and shielding guide lines
  2. In CCS if I exclude DP83869 and build with DP83826 it gives the above error     
  • Hi Kannabiran Krithivasan,

    Thank you for referring your query to the TI SITARA Processors Hardware Applications support team !

    Share a reference design of PHY with M12 /4 Wire termination and shielding guide lines

    As per my research, none of the AM243x and AM64x EVMs or Ethernet-based industrial communication evaluation modules adapts an M12 x 4 connector. It's likely that TI haven't tested / assessed / characterized behavior on SITARA EVMs the Ethernet communication with a M12x4 compatible cable. 

    Please refer this thread (despite usage of a different PHY and transformer) which provides information on a custom board which adapts a shielded ground plane receptacle using the DP83867e PHY: DP83867E + magnetics + Non-RJ45 connector

    In CCS if I exclude DP83869 and build with DP83826 it gives the above error

    The DP83826x PHYs do NOT support RGMII, only RMII and MII. And I can see your Sysconfig AM243x EthernetIP0 specifies RGMII. Could be this related to the build failure reason ?

    Looking forward to your feedback !

    Best Regards,

    Anastas Yordanov

  • Tried changing to MII but the error remains. Observation as long as DP83869 in not excluded there is no error. Will both PHY be compiled together always ? 

  • Hello Kannabiran,

    I will let our AM243x Ethernet PHY / MDIO software driver expert answer your question -  how to have only the DP83826x PHY included and build without errors.

    Please expect that there may be some delay depending on the expert's current availability / workload in the team.

    Thank you for your patience !

    Best Regards,

    Anastas Yordanov 

  • Hi Kannabiran, 

    The reason for errors in the compilation is because of the missing driver module inclusion in the build. By default, the DP83869 PHY driver is included. But for DP83826, you would have to follow the custom phy integration guide to add the new phy driver to compilation. This includes not only the inclusion of driver in the build, but also updating the params in the phy detect logic to include searching for dp83869. The error point to a situation where you have removed the DP83869 from the build, but the detect logic isn't updated. 

    Please let me know if this method works for you. If not, I would have to take a deeper. 

    Thanks and regards,
    Teja.