TIMER1 hangs within a s132 timeslot

RE: TIMER1 hangs within a s132 timeslot

Sigurd — Mon, 09 Oct 2017 15:41:19 GMT

See this post about debugging.

RE: TIMER1 hangs within a s132 timeslot

Sigurd — Mon, 09 Oct 2017 15:40:38 GMT

Why do you think the board crashes? Have you tried debugging, and checked for a hardfault?

RE: TIMER1 hangs within a s132 timeslot

Sebastien Huet — Mon, 09 Oct 2017 15:35:33 GMT

Hi Sigurd.

I am using nrf52 sdk13.1 No error reported by app_check

When i say almost immediatly this is a between 10 & 30us instead of the 100us request.

Many thanks.

Seb

RE: TIMER1 hangs within a s132 timeslot

Sigurd — Mon, 09 Oct 2017 15:06:33 GMT

Hi,

Are you using mbed or any RTOS ?

Try to check the return codes from the sd_ functions. I.e. something like this:

uint32_t err_code;
err_code = sd_nvic_ClearPendingIRQ(TIMER1_IRQn);
APP_ERROR_CHECK(err_code);

err_code = sd_nvic_SetPriority(TIMER1_IRQn, NRF_APP_PRIORITY_LOW);
APP_ERROR_CHECK(err_code);

err_code = sd_nvic_EnableIRQ(TIMER1_IRQn);
APP_ERROR_CHECK(err_code);

I have tried with nrf_drv_timer but the timer fires immediatly or so.

With the CC value you have set, the TIMER will fire very fast indeed.