UARTE crash

RE: UARTE crash

Lurn_Z — Thu, 03 Aug 2023 08:48:25 GMT

OK, I will try it, thanks a lot.

RE: UARTE crash

Susheel Nuguru — Thu, 03 Aug 2023 07:13:56 GMT

[quote user="Lurn_Z"]That is my bad, thanks for pointing this out. Maybe I should define a "RTC_TICKS_TO_US/MS"?[/quote]

I think you should just use the RTC counter value..Tick is nothing else but an event generated at every increment of the counter. If you have configured the prescaler same for blink_rx_rtc and rtos_rtc , then the counter value and the rtos tick should be the same.

RE: UARTE crash

Lurn_Z — Wed, 02 Aug 2023 08:08:45 GMT

[quote userid="6207" url="~/f/nordic-q-a/102304/uarte-crash/439426"]Are you using some FIFO for uart buffers or are your tying to send the uart data synchronously one by one. It is understandable that if you try to send another packet while the first one is not processed (due to probably processing delays on your system, priority of uart driver etc) then the second one shows busy.[/quote]

Yes, I realized the problem yesterday, the best way is send the uart data synchronously one by one, but now it throws error, and I'm using fifo to test it.

[quote userid="6207" url="~/f/nordic-q-a/102304/uarte-crash/439426"]I am not sure what the prescaler here is. [/quote]

I am using the default RTC configuration.

#define NRFX_RTC_DEFAULT_CONFIG                                                     \
{                                                                                   \
    .prescaler          = RTC_FREQ_TO_PRESCALER(NRFX_RTC_DEFAULT_CONFIG_FREQUENCY), \
    .interrupt_priority = NRFX_RTC_DEFAULT_CONFIG_IRQ_PRIORITY,                     \
    .tick_latency       = NRFX_RTC_US_TO_TICKS(NRFX_RTC_MAXIMUM_LATENCY_US,         \
                                               NRFX_RTC_DEFAULT_CONFIG_FREQUENCY),  \
    .reliable           = NRFX_RTC_DEFAULT_CONFIG_RELIABLE,                         \
}

[quote userid="6207" url="~/f/nordic-q-a/102304/uarte-crash/439426"]But using RTC_US_TO_TICKS is wrong when you are getting the rtc raw counter as the first argument.[/quote]

That is my bad, thanks for pointing this out. Maybe I should define a "RTC_TICKS_TO_US/MS"?

RE: UARTE crash

Susheel Nuguru — Wed, 02 Aug 2023 07:49:02 GMT

[quote user="Lurn_Z"]

Lurn_Z said:
it should be good in 32bytes per 1ms, but sometimes I will get error=17 (busy), and I will get a lot error = 17 in 64bytes per 1ms it should be good too, I don't know why

Can you consider what would affect it?

[/quote]

Are you using some FIFO for uart buffers or are your tying to send the uart data synchronously one by one. It is understandable that if you try to send another packet while the first one is not processed (due to probably processing delays on your system, priority of uart driver etc) then the second one shows busy.

I would also double check the uart interrupt priorities and would use the max priority allowed for the application if throughput is most important for your use case.

    NRF_LOG_DEBUG("blink_rx_rtc = %d.", RTC_US_TO_TICKS(nrf_drv_rtc_counter_get(&m_rtc), RTC_DEFAULT_CONFIG_FREQUENCY));

I am not sure what the prescaler here is. But using RTC_US_TO_TICKS is wrong when you are getting the rtc raw counter as the first argument.

RE: UARTE crash

Lurn_Z — Mon, 31 Jul 2023 09:22:40 GMT

[quote userid="6207" url="~/f/nordic-q-a/102304/uarte-crash/438930"]You need to use the HWFC by using two extra pins (RTS/CTS) on both devices.[/quote]

Sorry to say that another didn't support HWFC. So I can't use the HWFC

[quote userid="123170" url="~/f/nordic-q-a/102304/uarte-crash/438874"]it should be good in 32bytes per 1ms, but sometimes I will get error=17 (busy), and I will get a lot error = 17 in 64bytes per 1ms it should be good too, I don't know why[/quote]

Can you consider what would affect it?

About the RTC interval, in this link I was said the different RTC have different interval, and you suggested me to start the RTC at same time, but I forgot about this due to something, Now I'm back on this question because of a sync issue.

I used FreeRTOS, the FreeRTOS use the RTC1 in default. Now I use this code to config the RTC2 for test.

static void blink_rx_rtc_handler(nrf_drv_rtc_int_type_t int_type)
{
    ret_code_t err_code;
    NRF_LOG_DEBUG("blink_rx_rtc = %d.", RTC_US_TO_TICKS(nrf_drv_rtc_counter_get(&m_rtc), RTC_DEFAULT_CONFIG_FREQUENCY));
    NRF_LOG_DEBUG("rtos tick = %d.", xTaskGetTickCountFromISR());
    err_code = nrf_drv_rtc_cc_set(&m_rtc, BLINK_RTC_CC, BLINK_RTC_TICKS, true);
    nrf_drv_rtc_counter_clear(&m_rtc);
    APP_ERROR_CHECK(err_code);
}

void ppi_get_radio_init(void)
{
    ret_code_t err_code;

    err_code = nrf_drv_rtc_init(&m_rtc, &m_rtc_config, blink_rx_rtc_handler);
    APP_ERROR_CHECK(err_code);
    nrf_gpio_cfg_output(18);
    err_code = nrf_drv_rtc_cc_set(&m_rtc, BLINK_RTC_CC, BLINK_RTC_TICKS, true);
    APP_ERROR_CHECK(err_code);
    nrf_drv_rtc_enable(&m_rtc);
}

In the callback handler, the log shows like this. The interval is 100ms.

So logs shows the rtos tick interval is 99~100 ms, but the interval of RTC2 is 107.Do I need to do some conversions?

And I don't think turning on the RTC at the same time will have any effect. Because all values are for time intervals.

How to calibrate(maybe ?) the RTC2?

RE: UARTE crash

Susheel Nuguru — Mon, 31 Jul 2023 09:05:55 GMT

[quote user="Lurn_Z"]If use the HWFC, should I do any modify in hardware? And What configuration do I need to modify? Except change .hwfc = NRF_UARTE_HWFC_DISABLED to enable.[/quote]

You need to use the HWFC by using two extra pins (RTS/CTS) on both devices. These pin numbers needs to be configured when initializing UART. And else you need to change hwfc from disabled to enabled.

[quote user="Lurn_Z"]Can I use the PPI to trigger only once evnet? like when I get the event then I will enable the RTC2 via PPI. But just to enable it once time.[/quote]

No, you cannot make a hardwired PPI connection trigger only once. If the timing between the event generated and enabling RTC2 is not super critical to you, then I would suggest you enable the interrupt for that event and in the interrupt handler you enable the RTC2 on the first trigger. After this you can disable the interrupt generation for that event to avoid re-enabling RTC2 for every event generation.

RE: UARTE crash

Lurn_Z — Mon, 31 Jul 2023 01:33:36 GMT

Hi,

Yes, it should be good in 32bytes per 1ms, but sometimes I will get error=17 (busy), and I will get a lot error = 17 in 64bytes per 1ms it should be good too, I don't know why. And I didn't use the HWFC.

If use the HWFC, should I do any modify in hardware? And What configuration do I need to modify? Except change .hwfc = NRF_UARTE_HWFC_DISABLED to enable.

Update:

Q2:

Can I use the PPI to trigger only once evnet? like when I get the event then I will enable the RTC2 via PPI. But just to enable it once time.

RE: UARTE crash

Susheel Nuguru — Sun, 30 Jul 2023 13:29:40 GMT

[quote user="Lurn_Z"]

Q1:

Lurn_Z said:
Another question, did you have some suggestion to improve the speed to handle the packet when I send it via UARTE, or reduce delay in sending or receiving data?

Because I found that when I send 32bytes every 1ms, sometimes I will get the error = 17.

err_code = nrf_libuarte_async_tx(&libuarte, data_array, len);

But my baudrate = 1000000, it is enough to send it.

[/quote]

With the baudrate of 1000000 bits per second which is 125000 bytes per second you seems to be attempting to transfer 32000 bytes per second which should be decent. If you have HWFC enabled then maybe the peer UART might not be able to process the incoming bytes fast enough? I am not sure, but 32 bytes per 1ms seems pretty much doable on 1M baud rate.

[quote user="Lurn_Z"]If I want to use driver to set PPI, how can I get the address about this event?[/quote]

Maybe you want to use the below API from modules\nrfx\hal\nrf_radio.h

NRF_PPI->CH[5].EEP = nrf_radio_event_address_get(NRF_RADIO_EVENT_CRCOK);

RE: UARTE crash

Lurn_Z — Sun, 30 Jul 2023 10:36:54 GMT

Hi Susheel，

Actually, I still have two questions.

Q1:

[quote userid="123170" url="~/f/nordic-q-a/102304/uarte-crash/438646"]

Another question, did you have some suggestion to improve the speed to handle the packet when I send it via UARTE, or reduce delay in sending or receiving data?

Because I found that when I send 32bytes every 1ms, sometimes I will get the error = 17.

err_code = nrf_libuarte_async_tx(&libuarte, data_array, len);

But my baudrate = 1000000, it is enough to send it.

[/quote]

Q2:

[quote userid="123170" url="~/f/nordic-q-a/102304/uarte-crash/438703"]If I want to use driver to set PPI, how can I get the address about this event?[/quote]

NRF_PPI->CH[5].EEP = (uint32_t)&NRF_RADIO->EVENTS_CRCOK;

Best regards,

Lurn

RE: UARTE crash

Susheel Nuguru — Fri, 28 Jul 2023 10:17:03 GMT

Thanks for letting us know the whole chain of debugging and a solution.

RE: UARTE crash

Lurn_Z — Fri, 28 Jul 2023 09:07:11 GMT

Sorry I get something wrong I should reset the CC in callback handler.

static void blink_rtc_handler(nrf_drv_rtc_int_type_t int_type)
{
    nrf_drv_rtc_counter_clear(&m_rtc);
    nrf_drv_rtc_cc_set(&m_rtc, BLINK_RTC_CC, BLINK_RTC_TICKS, true);
    NRF_LOG_DEBUG("blink_rtc_handler.");
    APP_ERROR_CHECK(err_code);
}

Now it runs fine.

If I want to use driver to set PPI, how can I get the address about this event?

NRF_PPI->CH[5].EEP = (uint32_t)&NRF_RADIO->EVENTS_CRCOK;

change it to use driver like this

nrf_drv_ppi_channel_assign(m_ppi_channel1,
                                          nrf_drv_timer_event_address_get(&m_timer1,
                                                                          NRF_TIMER_EVENT_COMPARE0),
                                          nrf_drv_timer_task_address_get(&m_timer0,
                                                                         NRF_TIMER_TASK_STOP));

RE: UARTE crash

Lurn_Z — Fri, 28 Jul 2023 08:35:38 GMT

Sorry to say that I change from write the RTC registers to use the rtc driver, the ERROR 0 [NRF_SUCCESS] no longer occurs, and I will not get the all 0 data too.

But when I use nrf_drv_rtc_counter_clear() to clear the RTC counter, I found it didn't work.

static void blink_rtc_handler(nrf_drv_rtc_int_type_t int_type)
{
    nrf_drv_rtc_counter_clear(&m_rtc);
    NRF_LOG_DEBUG("blink_rtc_handler.");
    APP_ERROR_CHECK(err_code);
}

void ppi_rtc2_init(void)
{
    ret_code_t err_code;

    err_code = nrf_drv_rtc_init(&m_rtc, &m_rtc_config, blink_rtc_handler);
    APP_ERROR_CHECK(err_code);
    err_code = nrf_drv_rtc_cc_set(&m_rtc, BLINK_RTC_CC, BLINK_RTC_TICKS, true);
    APP_ERROR_CHECK(err_code);
    nrf_drv_rtc_enable(&m_rtc);
}

I can't clear the RTC counter in the rtc handler by nrf_drv_rtc_counter_clear().

what's wrong with it?

Best regards

RE: UARTE crash

Lurn_Z — Fri, 28 Jul 2023 07:05:59 GMT

I think the question is caused by PPI/RTC2, but I don't know why, because my uarte used RTC0.

void SWI3_EGU3_IRQHandler(void)
{
    /* Clear event register */
    NRF_EGU3->EVENTS_TRIGGERED[0] = 0;
    // to do
}

void SWI5_EGU5_IRQHandler(void)
{
    /* Clear event register */
    NRF_EGU5->EVENTS_TRIGGERED[0] = 0;
    NRF_RTC2->TASKS_CLEAR = 1;
    NRF_RTC2->TASKS_START = 1;
    // NRF_LOG_DEBUG("NRF_RTC2->TASKS_START.");
}

static void gpiote_init(void)
{
    NRF_GPIOTE->CONFIG[1] = (GPIOTE_CONFIG_POLARITY_LoToHi << GPIOTE_CONFIG_POLARITY_Pos)
                            | (18 << GPIOTE_CONFIG_PSEL_Pos)
                            | (GPIOTE_CONFIG_MODE_Event << GPIOTE_CONFIG_MODE_Pos);
}


/** @brief Function for initializing the PPI peripheral.
 */
void ppi_rtc2_init(void)
{
    gpiote_init();
    /* 6 is the default int. priority used in SDK drivers */
    NVIC_SetPriority(SWI5_EGU5_IRQn, 6);
    NVIC_EnableIRQ(SWI5_EGU5_IRQn);

    NRF_EGU5->INTENSET = EGU_INTEN_TRIGGERED0_Msk;

    NRF_PPI->CH[6].EEP = (uint32_t)&NRF_GPIOTE->EVENTS_IN[1];
    NRF_PPI->CH[6].TEP = (uint32_t)&NRF_EGU5->TASKS_TRIGGER[0];
    NRF_PPI->CHENSET = PPI_CHENSET_CH6_Msk;

    NRF_RTC2->CC[0] = RTC_US_TO_TICKS(SYNC_CYCLE_TIME, RTC_DEFAULT_CONFIG_FREQUENCY);
    NRF_RTC2->INTENSET = RTC_INTENSET_COMPARE0_Msk;
    /* Event signal must be enabled explicitly unlike most other peripherals */
    NRF_RTC2->EVTENSET = RTC_EVTEN_COMPARE0_Msk;

    /* 6 is the default int. priority used in SDK drivers */
    NVIC_SetPriority(SWI3_EGU3_IRQn, 6);
    NVIC_EnableIRQ(SWI3_EGU3_IRQn);

    NRF_EGU3->INTENSET = EGU_INTEN_TRIGGERED0_Msk;

    NRF_PPI->CH[4].EEP = (uint32_t)&NRF_RTC2->EVENTS_COMPARE[0];
    NRF_PPI->CH[4].TEP = (uint32_t)&NRF_EGU3->TASKS_TRIGGER[0];
    /* RTC does not have a SHORT to clear counter on compare match
       so using PPI instead */
    NRF_PPI->FORK[4].TEP = (uint32_t)&NRF_RTC2->TASKS_CLEAR;

    NRF_PPI->CHENSET = PPI_CHENSET_CH4_Msk;
}

when I call the ppi_rtc2_init() to config the PPI and RTC2, I will get the the ERROR 0 [NRF_SUCCESS], and get some packets get some data packets with all 0 data.

RE: UARTE crash

Lurn_Z — Fri, 28 Jul 2023 01:16:53 GMT

You can see my callback handler, I do call the nrf_libuarte_async_rx_free. But I still get the error.

Another question, did you have some suggestion to improve the speed to handle the packet when I send it via UARTE, or reduce delay in sending or receiving data?

Because I found that when I send 32bytes every 1ms, sometimes I will get the error = 17.

err_code = nrf_libuarte_async_tx(&libuarte, data_array, len);

But my baudrate = 1000000, it is enough to send it.

Best regards,

Lurn

RE: UARTE crash

Susheel Nuguru — Thu, 27 Jul 2023 14:26:09 GMT

This looks very much like the issue in this thread. You need to call nrf_libuarte_async_rx_free in the uart callback handler

RE: UARTE crash

Lurn_Z — Thu, 27 Jul 2023 10:06:22 GMT

And the irq handler.

void uart_event_handler(void *context, nrf_libuarte_async_evt_t *p_evt)
{
    nrf_libuarte_async_t *p_libuarte = (nrf_libuarte_async_t *)context;
    ret_code_t ret;
    buffer_t buf;
    switch (p_evt->type)
    {
        case NRF_LIBUARTE_ASYNC_EVT_ERROR:
            UART_PRINTF("NRF_LIBUARTE_ASYNC_EVT_ERROR = %d.", p_evt->data.errorsrc);
            break;
        case NRF_LIBUARTE_ASYNC_EVT_RX_DATA:
            memcpy(buf.p_data, p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);
            buf.length = p_evt->data.rxtx.length;
            ret = nrf_queue_push(&m_buf_queue, &buf);
            if (ret != NRF_SUCCESS)
                UART_PRINTF("In%s %d err_code = %d.", __func__, __LINE__, ret);
            // free the rx buffer
            nrf_libuarte_async_rx_free(p_libuarte, p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);
            break;
        case NRF_LIBUARTE_ASYNC_EVT_TX_DONE:
            break;
        default:
            UART_PRINTF("Unexpected LibUarte Event = %d.", p_evt->type);
            break;
    }
}