Timer0, Timer2 value = ?

[RixtronixLAB]

Dear Members,

NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 1, 2, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);

as define on NRF_LIBUARTE_ASYNC_DEFINE(_name, _uarte_idx, _timer0_idx,\
                                  _rtc1_idx, _timer1_idx,\
                                  _rx_buf_size, _rx_buf_cnt)

I used timer0 and RTC0 for UART0 and

RTC2,timer2 on UART1

How can I now the value of timer0,RTC0 and RTC2,Timer2 ?

is it 100mS each ?

Thanks

[RixtronixLAB]

where can I modify the timer value / prescaler ? thanks

[Einar Thorsrud]

Hi,

The libuarte driver uses NRFX_TIMER_DEFAULT_CONFIG for configuring the timer, and the prescaler is configured based on NRFX_TIMER_DEFAULT_CONFIG_FREQUENCY. So whatever is configured in sdk_config.h will be used. Note that you should also  change TIMER_DEFAULT_CONFIG_FREQUENCY in your sdk_config.h as that overwrites whatever NRFX_TIMER_DEFAULT_CONFIG_FREQUENCY is set to.

[RixtronixLAB]

Thanks for the reply Einar,

Will the timer effect "Event handler" of my UART ?

When I use callback function, the message from UART1 is cut .

case NRF_LIBUARTE_ASYNC_EVT_RX_DATA:
                  //nrf_libuarte_async_tx(&libuarte, p_evt->data.rxtx.p_data, p_evt->data.rxtx.length);--> with this function --> the messages are good

                   GPS_CallBack(); ---> with this function, a lot of messages in buffer are gone

is it because of the timer ?

[Einar Thorsrud]

Hi,

I do not see any reason this should be related to which timer you use. The instances are in principle identical. It sounds more like there may be an issue with perhaps a buffer being full or similar. I cannot say more though as I do not know anything about your code (GPS_CallBack() is not a function in the SDK so I do not know what you do there).