Timer0, Timer2 value = ?

RE: Timer0, Timer2 value = ?

Einar Thorsrud — Fri, 05 Feb 2021 17:18:24 GMT

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).

RE: Timer0, Timer2 value = ?

RixtronixLAB — Fri, 05 Feb 2021 14:23:09 GMT

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 ?

RE: Timer0, Timer2 value = ?

Einar Thorsrud — Fri, 05 Feb 2021 13:03:01 GMT

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.

RE: Timer0, Timer2 value = ?

RixtronixLAB — Fri, 05 Feb 2021 11:49:32 GMT

where can I modify the timer value / prescaler ? thanks