DMA using USART3 on STM32H7 part
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-09-26 2:30 PM
I am trying to get the USART3 to work with DMA, and so far have been unable to. After the initial cubeIDE project setup, I verified that standard (non DMA) RX and TX were working fine.
Moving to DMA, I was getting Direct Mode Error interrupts, and a little bit of digging showed me that the buffers I was using to send data were located in the DTCM ram. Changing that to move it to the D2 Space (starting at 0x3000000), and verifying the map file, I don't get Direct mode error interrupts, but I get no transmission of any bytes either.
Any thoughts or suggestions as to why DMA would not work on usart3? (FYI, I am using DMA successfuly on the SAI peripheral, so I know that DMA2 is working - USART uses DMA1). Thanks
Solved! Go to Solution.
- Labels:
-
DMA
-
STM32H7 Series
-
UART-USART
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-09-30 2:24 AM
Hello @Community member ,
Were you able to resolve the issue?
It will be interesting to share with us your update or the solution you found.
Please let me know if the answer proposed by @Georgy Moshkin or @Community member solved your issue? If yes, please "Select as Best" button.
If not, maybe you have the same issue as described in this post.
Imen
Thanks
Imen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-09-26 6:49 PM
Make use that you enabled "USART3 global interrupt" in NVIC Settings tab of "USART3 Mode and Configuration" of STM32CubeIDE configuration tool. STM32 HAL have some DMA-related code in USART interrupt handler. If it still does not work, please show how you call HAL functions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-09-27 12:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-09-30 2:24 AM
Hello @Community member ,
Were you able to resolve the issue?
It will be interesting to share with us your update or the solution you found.
Please let me know if the answer proposed by @Georgy Moshkin or @Community member solved your issue? If yes, please "Select as Best" button.
If not, maybe you have the same issue as described in this post.
Imen
Thanks
Imen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-10-04 8:11 AM
Changing the order of the code makes it work
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-10-04 8:16 AM
Glad to know you overcame this problem :)
So, You have the same issue as I already reported, and this will be resolved in the coming release of CubeMX.
Internal ticket 112040 (This is an internal tracking number and is not accessible or usable by customers)
Thanks for your contribution
Imen
Thanks
Imen
