STM32N6570-DK: How to integrate a custom Ethernet PHY (MXL86110I) driver

[GKarthik]

Hello,

I am working on an STM32N6570-DK project using NetX Duo generated through STM32CubeMX.

CubeMX provides PHY options such as RTL8211 and LAN8742. However, my hardware uses an MXL86110I-AQB-R Ethernet PHY connected through the RGMII interface.

I would like to know the recommended method for integrating a custom PHY driver when the required PHY is not available in CubeMX.

My questions are:

1. Can a project be generated using RTL8211 and then modified to use a custom MXL86110I PHY driver?

2. Which source files are responsible for PHY initialization, auto-negotiation, link status detection, and speed/duplex configuration?

3. Is there a PHY driver abstraction layer that custom PHY drivers must implement to work with the STM32 Ethernet driver and NetX Duo?

4. Are there any examples showing integration of a third-party PHY that is not listed in CubeMX?

5. What is the recommended approach for maintaining custom PHY support when regenerating code from CubeMX?

Project details:

• MCU: STM32N6570

• Board: STM32N6570-DK

• Middleware: NetX Duo

• PHY: MXL86110I-AQB-R

• Interface: RGMII

Any guidance would be appreciated.

Thank you.

[GKarthik]

Duplicate - merged.

Please don't start multiple threads on the same topic.

---

Hello,

I am working with the STM32N6570-DK board and using STM32CubeMX to generate a NetX Duo Ethernet project.

CubeMX currently provides support for PHY devices such as RTL8211 and LAN8742. However, my hardware design uses a MaxLinear MXL86110I Ethernet PHY connected through the RGMII interface.

I would like to understand the recommended approach for integrating a custom PHY driver into a CubeMX-generated project.

My questions are:

1. How should a custom PHY driver be added when the required PHY is not listed in CubeMX?
2. Is it recommended to initially generate the project using RTL8211 support and then replace the PHY-specific driver files with a custom MXL86110I driver?
3. Which files and interfaces are responsible for PHY initialization, link status monitoring, speed/duplex negotiation, and communication with NetX Duo?
4. Are there any STM32N6 Ethernet driver examples that demonstrate how to integrate a third-party PHY not officially supported by CubeMX?
5. Is there a standard PHY driver API that custom PHY drivers should implement to remain compatible with the STM32 Ethernet middleware and NetX Duo stack?

For reference:

• MCU: STM32N6570
• Middleware: NetX Duo
• PHY: MXL86110I-AQB-R
• Interface: RGMII
• Development Board: STM32N6570-DK

Any guidance, examples, or documentation references would be greatly appreciated.

Thank you.

[Pavel A.]

Please see reply from FBL here .

> Is it recommended to initially generate the project using RTL8211 support and then replace the PHY-specific driver files 

This is a good plan.