#define LAN8742A_PHY_ADDRESS

[john doe]

Posted on April 15, 2017 at 13:11

This bug has been reported before, but has survived a couple of cube version bumps.

STM32CubeMX 4.20.1 and f7_cube 1.6.1

in stm32f7xx_hal_conf.h it defines the PHY address incorrectly

#define LAN8742A_PHY_ADDRESS           1

should be

#define LAN8742A_PHY_ADDRESS           0

A symptom of this bug is HAL_ETH_ReadPHYRegister returning 0xFFFF for literally everything, and your cube-generated ethernet code won't work.

[lprobsth]

It is 2025 and this bug is still present.

I found it since link up and down events are not registered with the default configuration for ethernet and lwIP.

After changing the LAN8742A_PHY_ADDRESS both the link events and the relevant interrupt work.

I still wonder why this did not have an effect on the Basic Control Register (BCR) commands (or why nobody at ST was annoyed enough by this bug over the years).

[STOne-32]

Dear @lprobsth ,

Thank you for spotting again this confirmed issue , It will be logged In our Internal defect system . Sorry for the inconvenience that it may caused .

Regards,

STOne-32

[beetvdownload]

Thank you for identifying this issue again. It will be logged in our internal defect system. We apologize for any inconvenience this may have caused.
Beetvdownload.com