Incorrect order of initialization STM32H753

[MMüll.6]

The ADC and SPI use the DMA, but the CubeIDE initialize the DMA at last ant the SPI initialization fails. See screenshot.

CubeMX Version 6.6.1

Please fix this mistake. Attachment, the Screenshot.

The second problem: I cannot chage the "Rank" order from initialization.

The correct rank will be:

• first "SystemClock"
• second "GPIO"
• third "DMA"
• then the rest.

Other controllers like STM32G484 is the CubeMX code generation correct.

[Peter BENSCH]

Yes, this is a known issue and will be (hopefully) fixed soon, see e.g. here.

Does it answer your question?

Regards

/Peter

@Sara BEN HADJ YAHYA​ 

[MMüll.6]

Yes, thank you very much.

We have temporary fix this mistake with a user code before MX initializations:

__HAL_RCC_DMA1_CLK_ENABLE();

Regards Markus

[Pavel A.]

> see e.g. here.

But the OP has 6.6.1, a newer version. Regression?

[MMüll.6]

Yes, this bus is present in V6.6.1. Please fix it.

[Peter BENSCH]

This is also inexplicable to me, because I assumed that the problem had already been eliminated. But anyway, there are two ways to fix it:

• manually inserting __HAL_RCC_DMA1_CLK_ENABLE(); as you have done before
• moving the position of MX_DMA_Init already in CubeMX by selecting the row and moving it to the correct position with the small, easy-to-miss arrows above the table in the upper right corner

Regards

/Peter

[MMüll.6]

About your answer:

"moving the position of MX_DMA_Init already in CubeMX by selecting the row and moving it to the correct position"

Please mark me this "easy-to-miss arrows above the table", I cannot find it.

Attachment my CubeMX 6.6.1 View.

Regards Markus

[MMüll.6]

"because I assumed that the problem had already been eliminated"

No, the Problem is wihtin CubeMX 6.6.1 also pending. This mistakte is only fixed for a other µC.

[MMüll.6]

"because I assumed that the problem had already been eliminated"

No, the Problem is wihtin CubeMX 6.6.1 also pending. This mistakte is only fixed for a other µC.

[Peter BENSCH]

This is indeed an interesting behaviour, the small arrows are greyed out for DMA, among other things, as I was able to test just now. In a previous version, moving MX_DMA_Init was still possible. Our software team will take another look at this.

I'm very sorry, but until then, the only option is to insert it manually, as you have already done.

Regards

/Peter