AM2632: DP83867 Ethernet phy driver support in SDK

Michael Shklyarman

Part Number: AM2632
Other Parts Discussed in Thread: DP83869

Team,

my customer would like to use the above PHY in their design which seems to be very close to the DP83869 used on the Launchpad.

The two are from the same family and seem to be very close with pin compatible variants. I am looking for some guidance/suggestions as to what differences are there from basic SW driver perspective (assuming same RGMII connection) and what parts of the driver would require attention/changes when doing the porting.

thank you

Michael

over 1 year ago

0 Nilabh Anand over 1 year ago

TI__Mastermind 36293 points

Hi Mike,

Could you please share the following details:

1. Which example are the customer trying to use is it CPSW based or Industrial Ethernet based?

0 Nilabh Anand over 1 year ago in reply to Nilabh Anand

TI__Mastermind 36293 points

We also have this phy driver present in SDK if this is used in context of Enet LLD driver with CPSW or ICSSG.

The path for the same: \mcu_plus_sdk\source\networking\enet\core\src\phy

0 Michael Shklyarman over 1 year ago in reply to Nilabh Anand

TI__Genius 12550 points

Nilabh,

Thank you for the pointer. The customer plans to use CPSW. The question is about porting the driver in syscfg. Can they define Enet (CPSW) with no ETHPHY defined just like what is in enet_lwip_cpsw example and “hope” 83867 will work? Or they need to add EXTPHY following instructions from Adding Support for Custom PHY in the User Guide.

As a side note, it would be good to answer the above question in the UG and also point out to the drivers that are available in the SDK. Also, Ethernet PL pointed our that the drivers are now maintained in public Github: https://github.com/TexasInstruments/ti-ethernet-software/tree/main/rtos_drivers/src. A guidance on what and how to use when changing from the PHY used on TI EVM to some other PHY in cases where driver is available and where it isn't would be very useful.

thank you

Michael