ETH communication error due to cube mx version

[LeeJaewon]

In the version of cube mx 6.4.0 you can set parameters and advanced parameters, but in the version of cube mx 6.16.1 you can only select the chip in the platform setting in the LWIP in middleware.

I configured the firmware by installing the KSZ8863RLLI LAN driver in the STM32F407VET6 MCU. Cube IDE used version 1.18.1.

Ping test went well in the version of cube mx 6.4.0 and it doesn't work in the version of cube mx 6.16.1.

Is there a way to do it in the version of cube mx 6.16.1? What are the problems?

The 00.ETH file is the firmware created in the version of cube mx 6.4.0 and the 02.ETH_16.1 file is the firmware created in the version of cube mx 6.16.1

[Mahmoud Ben Romdhane]

Hello @LeeJaewon 

Let me thank you for posting.

I am currently checking this behavior, and I will get back to you ASAP.

Thanks.

Mahmoud

[Mahmoud Ben Romdhane]

Hello @LeeJaewon 

Could you provide please screenshots that illustrate the difference between 6.4.0 and 6.16.1.

Thanks.

Mahmoud

[LeeJaewon]

Hello

The left is cube.mx 6.4.0 and the right is 6.16.1.

The big difference, as shown in the photo, is that the advanced parameters exist only in the 6.4.0 version in the ETH category, and the platform settings exist only in the 6.16.1 version in the LWIP category.

Please check.

 

[Mahmoud Ben Romdhane]

Hello @LeeJaewon 

After checking internally, this behavior is expected.

Since STM32CubeMX 6.8.0, PHY Driver Settings must be configured from the LWIP "Platform Settings" not from the ETH such as the case with STM32CubeMX 6.4.0.

Thanks.

Mahmoud

[LeeJaewon]

hello

When I set up the platform in LWIP, I need to see detailed settings, but I don't have that part. Also, I can't set the speed of ETH.

Please check.

[Mahmoud Ben Romdhane]

Hello @LeeJaewon 

This is an expected behavior in recent STM32CubeMX versions.

Starting from STM32CubeMX 6.8.0, PHY configuration (speed, duplex, auto-negotiation, .) is no longer fully handled via CubeMX GUI.

The LWIP Platform Settings only allow selecting the PHY device, while detailed PHY parameters are managed at runtime by the driver.

Ethernet speed is determined through PHY auto-negotiation during initialization and cannot be forced from CubeMX.

If a fixed speed is required, it must be configured directly in the PHY driver or user code after initialization.

Functionally, this is equivalent to CubeMX 6.4.0 behavior.

Thanks.

Mahmoud