Skip to main content
mbarg.1
Senior III
December 4, 2024
Question

MORE BUGS STMCubeMX migration to v6.13 FW H7 V1.12 - ETH HAL

After experiencing more problems in legacy codes, we found that STM changed HAL drivers without any notice.

THIS CAN BE BLOCKING.

Example : 

((uint32_t)((pFilterConfig->BroadcastFilter == DISABLE) ? 1U : 0U) << 5) |

is NOW

((uint32_t)((pFilterConfig->BroadcastFilter == ENABLE) ? 1U : 0U) << 5) |

in

HAL_ETH_SetMACFilterConfig()

Only workaround:

SPEND all the time it needs and check all drivers carefully for changes.

stm32h7xx_hal_eth.c has dozen of changes, impossible to compare files and get differences easily.

 

This topic has been closed for replies.

3 replies

mƎALLEm
ST Technical Moderator
December 4, 2024

Hello,

Escalated internally for analysis. Internal ticket number: 197721 

Thank you for your contribution.

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
milorad
Associate II
December 9, 2024

In the same context, if the functionality of a setting (BroadcastFilter) is reversed how would the code that relied on the old functionality be able to handle that?
Also, this change is now present in some of the newly updated HALs, what about HALs for older families (even obsolete ones) that will probably never be updated?

mbarg.1
mbarg.1Author
Senior III
December 15, 2024

FW H7 V1.12.1 solves the bug

BUT once more, in release notes there is NO indication of this fix.