Clock Configuration bug for STM32H753ZI in STM32CubeMX v6.18.0

[FluxPower42]

Hi,

after Update to v6.18.0 we get the following warning:
 

Our configuration:
 

Mouse hover:

 

Obviously, you don't have a single source. Otherwise, it wouldn't be possible for the “240 MHz” label below the text field and for the “225 MHz” label to appear when hover over that same text field.
Please, ST, conduct more integration tests!
 
Attached our .ioc file.

[mƎALLEm]

Hello,

Thank you for your contribuition.

1- This post shouldn't be posted in STM32 MCU Products but rather in STM32CubeMx forum board. I move it then ..

2- I think the same issue raised in these threads:

STM32CubeMX clock validation regression: STM32H743VIHx VOS0 LDO HCLK 240 MHz incorrectly limited to 225 MHz

CubeMX Version 6.18.0 introcudes wrong check of clock limits for STM32H753

Potential bug in CubeMX 6.18.0 – Clock Configuration error

The issue is already has been taken by the team over the internal ticket number: CDM0064049.

[FluxPower42]

Yes, it is the same.
Where in the Known limitations - STM32CubeMX 6.18.0 documentation I can find this bug?

[mƎALLEm]

Yes, it is the same.
Where in the Known limitations - STM32CubeMX 6.18.0 documentation I can find this bug?

That’s the known limitations list (we are aware of before the release).

This one has been discovered after the release.