How can I process incoming UART communications when the code cycle is lengthy?

Forum|Forum|11 years ago
November 7, 2014
4 replies
932 views

Posted on November 07, 2014 at 08:54

I'm working with an STM32F4 Discovery board, and I've been experimenting with the CubeF4 UART examples (HAL).

Everything I've seen suggests that receiving takes a manual command.

Example:

HAL_UART_Receive(&UartHandle, (uint8_t *)aRxBuffer, RXBUFFERSIZE, 50);

Even the interrupt based examples look similar. Playing around with the polling version, I discovered that if each code cycle takes too long (can be simulated by adding a 100 ms delay), then the majority of incoming communications are lost. Increasing the timeout on the receive command can help, but then it slows down the code execution.

How can I have incoming communications processed immediately, with good success, without slowing down the rest of the code execution, and have the receive buffer act as a true buffer - holding the last communication even if the code cycle is lengthy?

This topic has been closed for replies.

ivani

Visitor II

Posted on November 08, 2014 at 18:46

The HAL drivers are a jungle of code but hardly useful...

A typical way to organize the communication is using of circular buffers for received (and transmitted) characters. The management of the buffers (i.e. receiving of incoming characters) could be done either via ISR, or by DMA. These buffers are separated from the application level by function calls, which return the requested number of characters (either blocking, or non-blocking), or fill the transmission buffers with characters to send.

Of course, the buffers (especially the Rx one) should be made big enough to fit the incoming characters for the maximal interval of inactivity between two servicing calls.