STM32H755: Wrong RCC clock auto configuration

[Peter3718]

Hi, @Amel NASRI 

By the way, RCC clock auto configuration is also wrong.

but result showing:

which will mess up UART baud rate ( I have to chage UART clock source to HSI to get correct UART output, the old is PCLK1), same issue as the post you linked.

CubeMX 6.13.0 and MCU Package H7 v1.12.0 produce i... - STMicroelectronics Community

These issues are fundamental, need to be resloved with high priority.

Peter

[Amel NASRI]

Hi @Peter3718 ,

Let us handle this issue in a separate thread (from the original one: Why is USE_PWR_LDO_SUPPLY defined by default when generating a project in CUBEMX?).

I keep @Ghofrane GSOURI in the loop to investigate the case.

-Amel

[Amel NASRI]

Hi again @Peter3718 ,

Checking again, it looks like you are facing the same issue as the one reported here.

This should be already fixed the patch 1.12.1 of STM32CubeH7 package.

Could you please update the firmware with this patch and let me know if you still have the same problem or not?

-Amel

[Peter3718]

Hi @Amel NASRI ,

I was aware that 1.12.1 has a bug fix about RCC. But the wrong result is with the latest firmware 1.12.1 and 6.13.0 MX

peter

[Amel NASRI]

OK I get it. It looks like STM32CubeMX generated code doesn't consider the updated template for system_stm32h7xx_dualcore_boot_cm4_cm7.c. I reported this issue internally (199524).

The correct one should be based on the template available under STM32Cube_FW_H7_V1.12.1\Drivers\CMSIS\Device\ST\STM32H7xx\Source\Templates.

In the file <generated_prj>/Common/Src/system_stm32h7xx_dualcore_boot_cm4_cm7.c, try to replace:

const  uint8_t D1CorePrescTable[16] = {0, 0, 0, 0, 0, 0, 0, 0, 1, 2, 3, 4, 6, 7, 8, 9};

by

const  uint8_t D1CorePrescTable[16] = {0, 0, 0, 0, 1, 2, 3, 4, 1, 2, 3, 4, 6, 7, 8, 9};

That should fix the issue.

-Amel

[Peter3718]

Hi, @Amel NASRI 

This manual change can fix the issue.

hope to see fix in auto generation.

Peter