TM4C12x UART termination character

And it is said that "vultures" descend quickly on the plain Serengeti...

First, thank you all for very quick response, and you are right I was sending that, stupid of me not to figure that before, in win app i was using serialPort.WriteLine(), I suppose it adds this character for a new line. Sorry for asking the stupid question, nevertheless I got useful information of it.

MCU only receives frame, and according to data received it will start a relay or something not sure jet, but nothing that needs quick response and not much of data will be sent but I need it to listen and to be able to receive UART data at any moment.

Mr. Ashara you mentioned stop condition, how can I check if this condition is met? This is my interrupt routine, I was thinking to check if

This is my interrupt routine, I was thinking to check if the character is some character that I insert myself on the end of the string (ch_EOT) and if it is I raise flag and process incoming data. Can you advise me to do something more suitable? I also do not like on inserting myself some character, since this will be embedding in the application form the third party?

void UART0_ISR(void)
{
	uint32_t ui32Status;
	ui32Status = UARTIntStatus(UART0_BASE, true);
	UARTIntClear(UART0_BASE, ui32Status);
	if(ui32Status&UART_INT_TX)
	{
		TXcount++;
	}

	while(UARTCharsAvail(UART0_BASE)) //loop while there are chars
	{
		incoming[i]=UARTCharGet(UART0_BASE);
		UARTCharPut(UART0_BASE, incoming[i]); //echo character
		if(input[i]==ch_EOT)
		{
			flag_EOT_RS485=1;
			//i=0;
		}
		else
		{
			flag_EOT_RS485=0;
			i++;
		}

	}
}

Yes, I understand, sorry for being bit confused it's been a long day. Thing is that, for example if I send

'abcd'

I count 5 interrupts triggered (4 letters + '\n'). So I'm using this condition in the end to know when full string is received, I referred to it as a frame. So when You mentioned :

"The UART frame has a stop condition in the frame itself. "

I thought it would be at the end of a string, but actually, it is at the end of the byte. FIFO is disabled in UART config function.

Hi,

You should specify what kind of "data" you transfer over UART - either pure text, and in this case the LF character should be precessed as its name said or the data is binary - e.g the number 0x3F0A is sent LSB first, so first is 0x0A and should not be removed or any other action taken on it.

Take care with your PC application, there are some other hidden problem(s) with drivers/software from MS (i.e, 0x0 has also a special treatment).