nRF9160 flush UART buffer.

RE: nRF9160 flush UART buffer.

Baowz — Thu, 02 Dec 2021 08:53:28 GMT

Thank you! I will test this out.

RE: nRF9160 flush UART buffer.

Susheel Nuguru — Thu, 02 Dec 2021 07:31:32 GMT

Very crude code below, but goes something like this

If you have

uart_irq_callback_set(dev, uart_irq_handler);

then in

static void uart_irq_handler(const struct device *dev, void *context)
{
	uint8_t buf;
	while (uart_irq_rx_ready(dev)) {
		uint8_t buf[10];
		int len = uart_fifo_read(dev, buf, sizeof(buf));

		if (len) {
			printk("read %d bytes\n", len);
		}
	}
}

RE: nRF9160 flush UART buffer.

Baowz — Wed, 01 Dec 2021 16:28:55 GMT

Not flushing TX should be fine, it's the RX that receives the biggest amount of data. When you say that it party works and manually flush the RX by reading the whole RX fifo. Do you mind showing me an example of how you would use uart_fifo_read in this case? It would be much appreciated!

RE: nRF9160 flush UART buffer.

Susheel Nuguru — Wed, 01 Dec 2021 13:59:24 GMT

partly. This callback is called when there is uart irq triggered nd you can atleast manually flush the rx by reading the whole rx fifo using uart_fifo_read. There is no API natively to flush TX fifo as deep as i can see.

RE: nRF9160 flush UART buffer.

Baowz — Tue, 30 Nov 2021 17:59:20 GMT

I've added "uart_irq_callback_set(uart, uart_cb)" to the last code snipped instead of k_free(read_buf). The code is not rebooting and might be a solution. Does it seem correct?

RE: nRF9160 flush UART buffer.

Baowz — Tue, 30 Nov 2021 17:05:30 GMT

These are the cases the buffer is being used:

/* Buffers for reading UART */
static uint8_t uart_buf[64];
uint8_t read_buf[READ_BUF_SIZE];
uint32_t read_buf_ptr = 0;

void uart_cb(struct device *x) {
	uart_irq_update(x);
	int data_length = 0;

	if (uart_irq_rx_ready(x)) {
		data_length = uart_fifo_read(x, uart_buf, sizeof(uart_buf));
		uart_buf[data_length] = 0;
	}

    // Considering it reads just one character per time
	uint8_t read_char = uart_buf[0];
	read_buf[read_buf_ptr] = read_char;
    read_buf_ptr++;
}

I can elaborate further on the code if you have any questions.

the usage of k_free is more a desperate measure than a reasonable one given the lack of alternatives. I saw it being used in one of Nordics UART samples and tried to recreate it.

RE: nRF9160 flush UART buffer.

Susheel Nuguru — Tue, 30 Nov 2021 12:38:18 GMT

app_uart_flush was relying on app_fifo_flush. Fifos are application level buffers that could be controlled in app, but I do not think you can do that when you are using Zephyr system calls to interfact with UART driver.

[quote user=""]I've tried to use k_free(*name of buffer*), but I'm not certain if this is the correct function. The board just ends up rebooting as soon as it reaches this part of the code.[/quote]

Not sure why you are trying k_free here, are the buffers dynamically allocated? if so how k_free would help communicating with the uart driver to flush the driver.

Can you add more code snippets on how you are using read_buf in your code, i am confused by the use of k_free on the buffers and your interpretation of connecting this to uart?