Hi everyone:
I want to use UARTE on my FreeRTOS, but when I used the example(examples/peripheral/libuarte) in rtos, something went wrong.
First of all, I tested the example, and it looks like good. When I send slowly, the uart log is here.
and when I send quickly(every 4ms), the uart log is that.
But when I use the UARTE in FreeRTOS, It looks OK when sending slowly, but when I send it every 4ms(I need this frequency), the result is here.
I don't know what's wrong.
Best regards,
Lurn
Sorry for my unclear description.
I use the example uarte code in FreeRTOS, just modify here
nrf_libuarte_async_config_t nrf_libuarte_async_config = {
.tx_pin = TX_PIN_NUMBER,
.rx_pin = RX_PIN_NUMBER,
.baudrate = NRF_UARTE_BAUDRATE_921600,
.parity = NRF_UARTE_PARITY_EXCLUDED,
.hwfc = NRF_UARTE_HWFC_DISABLED,
.timeout_us = 2,
.int_prio = APP_IRQ_PRIORITY_HIGH,
.pullup_rx = 1
};
I change the int_prio from APP_IRQ_PRIORITY_LOW to APP_IRQ_PRIORITY_HIGH.
the question is when I use FreeRTOS,when I'm done sending the data, I should receive the data immediately, the log should like that, (the ->◇ is send data, <- 
is receive data).
But now, I get a wrong state, I only receive some data after I send it several times
BR,
Lurn
Maybe I've entered a misunderstanding, my device need receive 32bytes data per 4ms, and process it.
So, for my test, I shouldn't print it by UART after receive data, because TX also spend time?
I modified the way to print the log (it will be display by RTT now),but it still many wrong formats.
logs like that, I send 32B data (ZZZ.....for test), Sometimes it is split into two parts
void uart_event_handler(void * context, nrf_libuarte_async_evt_t * p_evt)
{
....
switch (p_evt->type)
{
...
case NRF_LIBUARTE_ASYNC_EVT_RX_DATA:
// ret = nrf_libuarte_async_tx(p_libuarte,p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);
ret = 0;
buffer_t buf = {
.p_data = p_evt->data.rxtx.p_data,
.length = p_evt->data.rxtx.length,
};
if (ret == NRF_ERROR_BUSY)
{
ret = nrf_queue_push(&m_buf_queue, &buf);
APP_ERROR_CHECK(ret);
}
else
{
APP_ERROR_CHECK(ret);
}
m_loopback_phase = true;
memcpy(data_array, buf.p_data, buf.length);
flag = 1;
nrf_libuarte_async_rx_free(p_libuarte, p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);
break;
...
break;
}
}
I modify the timeout to 10 or 100 or 1000, it looks like same..
timeout is 100us in this logs.
here is no data loss, though - only that you got two events for what I assume conceptually was one transaction
Yes, I think so, the data is not lost, just became two parts.
You will get data when there is a timeout (packet boundary) or when the Rx buffer is full.
I think it's really about Rx buffer, cause when I change the buffer size from 256 to 64 the data was be split earlier.
NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 64, 3);
But, the rx buffer was cleared everytime I received data.
I used that nrf_libuarte_async_rx_free(p_libuarte, p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);
Do you have any other solution?
And I have another question that I need a frequency of 500 times per second, but when I test the application,I don't think it can reach this frequency. Because I get the logs in 9 second, it just 260 times data. Also I will check the sender frequency, and I hope you can give me some suggestions.
BR,
Lurn
After my test, Here is 3 questions.
I send 32 bytes, the data head is A5 C5, and print 34 bytes so the last two data should be 0.
(uint8_t data_array[256] = {0};)
1. When the sender sending data slowly, about 25 times per second, logs looks like that.
After receiving several pieces of data, one of it was split into two parts
2. When the sender sending data quickly, (250 times per second), data will be lost, Only 30 pieces of data are received per second.
3. When the sender sending data quickly, (250 times per second), logs looks like that.
There is an exception in the data format,
Hope you can give me some suggestions.
BR,
Lurn