In this guide, we shall use buffer of 5 characters for the reception and 40 for the transmission.<\/p>\n\n\n\n
Also, declare two volatile variables to indicate the end of transmit and receive as following:<\/p>\n\n\n\n
volatile uint8_t TxFinished, RxFinished;<\/pre><\/div>\n\n\n\nIn STM32G0xx_hal_uart.c, we can find two functions shown below:<\/p>\n\n\n\n
<\/p>\n\n\n\n<\/p>\n\n\n\n
First function is:<\/p>\n\n\n\n
<\/p>\n\n\n\n
\/**\n * @brief Tx Transfer completed callback.\n * @param huart UART handle.\n * @retval None\n *\/\n__weak void HAL_UART_TxCpltCallback(UART_HandleTypeDef *huart)\n{\n \/* Prevent unused argument(s) compilation warning *\/\n UNUSED(huart);\n\n \/* NOTE : This function should not be modified, when the callback is needed,\n the HAL_UART_TxCpltCallback can be implemented in the user file.\n *\/\n}<\/pre><\/div>\n\n\n\nThis function is called when the UART has finished transmitting all the data.<\/p>\n\n\n\n
<\/p>\n\n\n\n
The other function:<\/p>\n\n\n\n
\/**\n * @brief Rx Transfer completed callback.\n * @param huart UART handle.\n * @retval None\n *\/\n__weak void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart)\n{\n \/* Prevent unused argument(s) compilation warning *\/\n UNUSED(huart);\n\n \/* NOTE : This function should not be modified, when the callback is needed,\n the HAL_UART_RxCpltCallback can be implemented in the user file.\n *\/\n}<\/pre><\/div>\n\n\n\nThis function will be called when the number of characters has been received.<\/p>\n\n\n\n
These two functions are declared as weak which can be overwritten by the user.<\/p>\n\n\n\n
After the volatile variable, we shall implement the functions as following:<\/p>\n\n\n\n
void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart)\n{\n\tRxFinished=1;\n\n\n}\n\nvoid HAL_UART_TxCpltCallback(UART_HandleTypeDef *huart)\n{\n\tTxFinished=1;\n\n}<\/pre><\/div>\n\n\n\n<\/p>\n\n\n\n
In the Rx function, set RxFinished to 1 and same thing for Tx function by setting the TxFinished to 1.<\/p>\n\n\n\n
<\/p>\n\n\n\n
In user code begin 2:<\/p>\n\n\n\n
Start the UART receive in DMA mode as following:<\/p>\n\n\n\n
HAL_UART_Receive_DMA(&huart2, RxData, 5);<\/pre><\/div>\n\n\n\n<\/p>\n\n\n\n
In user code 3 in while 1 loop:<\/p>\n\n\n\n
First, check if the UART has receive all the characters as following:<\/p>\n\n\n\n
if(RxFinished==1)<\/pre><\/div>\n\n\n\nIf there is new data, <\/p>\n\n\n\n
We shall echo back the characters to be received as following:<\/p>\n\n\n\n
uint32_t len=sprintf((char*)TxData,"Received Data are %c %c %c %c %c \\r\\n",\n\t\t\t\t RxData[0],RxData[1],RxData[2],RxData[3],RxData[4]);<\/pre><\/div>\n\n\n\nSince sprintf return the number of characters , we shall use it when transmit the data.<\/p>\n\n\n\n
Next, send the data over UART using DMA as following:<\/p>\n\n\n\n
HAL_UART_Transmit_DMA(&huart2, TxData, len);<\/pre><\/div>\n\n\n\nSet the RxFinished back to 0.<\/p>\n\n\n\n
RxFinished=0;<\/pre><\/div>\n\n\n\nWait until the TxFinished is set (This part is depending on your application)<\/p>\n\n\n\n
while(TxFinished==0);<\/pre><\/div>\n\n\n\nSet back the TxFinish back to 0:<\/p>\n\n\n\n
TxFinished=0;<\/pre><\/div>\n\n\n\n<\/p>\n\n\n\n
Thats all for the code.<\/p>\n\n\n\n
<\/p>\n\n\n\n
3. Results:<\/h2>\n\n\n\n Using any serial port program, set the baud rate of 115200, send any 5 characters without \\r\\n and see the echoed characters.<\/p>\n\n\n\nHappy coding\u00a0\ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
In the previous guide (here), we took a look how to receive data over UART using interrupt. Now, we shall see how to send and receive data over UART using DMA. In this guide, we shall cover the following: Adding the DMA capability. Developing the code. Results. 1. Adding The DMA Capability: By continue from […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,11,12],"tags":[],"class_list":["post-2357","post","type-post","status-publish","format-standard","hentry","category-embedded-systems","category-peripheral-drivers","category-stm32"],"_links":{"self":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/2357"}],"collection":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2357"}],"version-history":[{"count":1,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/2357\/revisions"}],"predecessor-version":[{"id":2362,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/2357\/revisions\/2362"}],"wp:attachment":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"https:\/\/blog.embeddedexpert.io\/wp-content\/uploads\/2024\/02\/pt156578902-100_original_arm_mcu_stm32g070kbt6_stm32g070_stm32g_lqfp_32_microcontroller.jpg-2-1.webp\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/blog.embeddedexpert.io\/wp-content\/uploads\/2024\/02\/2024-02-17_16-11-04-1024x572.jpg\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.embeddedexpert.io\/wp-content\/uploads\/2024\/02\/2024-02-17_16-24-06-1024x572.jpg\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.embeddedexpert.io\/wp-content\/uploads\/2024\/02\/2024-02-15_16-11-28-1024x738.jpg\")
<\/figure>\n\n\n\n