STMCubeIDE 1.1.0 (CubeMX 5.4.0) switch initialization order.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-11-14 12:10 PM
Hi. I noticed in the latest STMCubeIDE v1.1.0 DMA is initialized at the end of initialization chain. There is only NVIC interrupt priority set but as i can see it's important where it's initialized.
/* Initialize all configured peripherals */
MX_GPIO_Init();
MX_USART2_UART_Init();
MX_DMA_Init();
instead of previous
/* Initialize all configured peripherals */
MX_GPIO_Init();
MX_DMA_Init();
MX_USART2_UART_Init();
The result is while UART IDLE interrupt occurs, DMA shows me always that is received 0 bytes in NDTR register.
my code(working with correct initialization order): https://github.com/lamik/UART_DMA_receiving
- Labels:
-
ADC
-
Bug-report
-
DMA
-
Github
-
STM32F1 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-11-17 10:44 PM
Having the same problem, generating code for a STM32F100VETx while using ADC1 and DMA. DMA is initialized after ADC1 which does not work if DMA is used to query the ADC. Switching the initialization order resolves the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-11-19 11:38 PM
Same problem appears on CubeMX5.4.