The STM32G484CETx initialization code generated by STM32cubeMX has a bug

Is this a project created in some older CubeMX version?

https://community.st.com/s/question/0D50X0000Bwjgi7SQA/with-stm32cubemx-55-and-stm32h743-the-mxdmainit-function-is-not-called-at-the-right-time

JW

(collecting thread https://community.st.com/s/question/0D50X0000Bmob3uSQA/dma-not-working-in-cubemx-generated-code-order-of-initialization )

Still broken.

Last week I downloaded and installed

STM32CubeIDE

Version: 1.7.0

Build: 10852_20210715_0634 (UTC)

which seems to contain

STM32CubeMX - STM32 Device Configuration Tool

Version: 6.3.0-RC5

Build: 20210714-1111 (UTC)

This is the autogenerated code for the Nucleo-F303ZE after I enable ADC and play with sending strings over USART. Later I enabled DMA to figure out how it works to transmit on USART using DMA. (Not sure if the order is important, but just to tell you how I got to this point)

/* USER CODE END SysInit */
 
 /* Initialize all configured peripherals */
 MX_GPIO_Init();
 MX_RTC_Init();
 MX_USART3_UART_Init();
 MX_USB_PCD_Init();
 MX_DMA_Init();
 MX_ADC1_Init();
 /* USER CODE BEGIN 2 */

I noticed in the debugger that the CCR register didn't seem to accept the value written to it in the MX_DMA_Init(), and I couldn't change it from inside the debugger either.

My workaround was to place a call to MX_DMA_Init() in the User Code just above, but it took me basically an entire day of headscratching before a colleague found this thread and showed it to me.