cancel
Showing results for 
Search instead for 
Did you mean: 

[BUG] D.T.C.C.G. produces MX_DMA_Init in wrong position? (USART/SPI - STM32CubeIDE 1.9.0)

Not applicable

0693W00000Nqk4AQAR.png 

"A regression was detected in the previous STM32CubeMX version 6.3.0 (STM32CubeIDE Version: 1.7.0 generating a wrong order of initialization functions.

This issue was fixed in the latest STM32CubeMX version 6.4.0. Thus, newly created project with this version will generate the correct initialization functions order."

https://community.st.com/s/question/0D53W00001EzCmCSAV/mxdmainit-order-in-the-mainc-file-generated-by-stm32cubemx-how-to-fix?t=1653614837707

"And then called these initialization functions manually in the following user code segment, and now it looks like this"

https://stackoverflow.com/questions/70558087/stm32-spi-ll-dma-transmit

"I couldn't solve it without solving the same problem. But this solution really works. I can't understand why CubeMX is generating wrong code."

https://community.st.com/s/question/0D50X0000AxEm8USQS/solved-spi-dma-doesnt-transmit-anything-is-my-configuration-wrong

1 ACCEPTED SOLUTION

Accepted Solutions
Sara BEN HADJ YAHYA
ST Employee

hello @rtek1000​ ,

Thanks for your feedback,

This is a known issue and it will be fixed soon, for more details please check my answer in this thread.

Sara.

View solution in original post

4 REPLIES 4
Sara BEN HADJ YAHYA
ST Employee

hello @rtek1000​ ,

Thanks for your feedback,

This is a known issue and it will be fixed soon, for more details please check my answer in this thread.

Sara.

Hello, thanks for the answer. Do you have a list that I can see what issues I might have that are known and could not be resolved yet? At least for the F4 and H7 line. Thanks.

Hello @rtek1000​ ,

I apologize but we don't have a list. Please if you have any concern or a doubt about anything don't hesitate to create a thread for it and we will do the analysis and provide you with an answer.

Sara.

Sara BEN HADJ YAHYA
ST Employee

Hello @rtek1000​ ,

This issue is fixed in STM32CubeMX latest release.

V6.6.0 is now available under this Link.

Thanks for your contribution.

Sara.