apply timeslot ,Causes the timer to fail to start (nRF52832 SDK15.3 s132 ESB+timeslot)

[zxcv7063]

Hi All:

       Applyed the under timeslot : 

       

       causes some peripherals(eg:static const nrf_drv_timer_t m_timer = NRF_DRV_TIMER_INSTANCE(2)) no access interrupt,

       what 's the matter? 

[Sigurd]

Hi,

What do you mean by "no access interrupt" ? Please elaborate

[zxcv7063]

Hi:

•     Not  called the above timeslot, peripheral timer(nrf_drv_timer_t m_timer = NRF_DRV_TIMER_INSTANCE(2)) Can enter callback normally. code snippet: 
• void timer_handler(nrf_timer_event_t event_type, void * p_context)
  {
  
  switch (event_type)
  {
  case NRF_TIMER_EVENT_COMPARE0:
  NRF_LOG_INFO("AD time....\r\n");
  break;
  default:
  //Do nothing.
  break;
  }
  
  }
• The following print:

    

    But called the above timeslot ,timer  cannot enter callback properly.There's no print on it.

[Sigurd]

1) Are you doing anything with TIMER2 in radio_callback() ?

2) Does it start to print again when you exit radio_callback()/ the timeslot ? 

3) Any difference in behavior if you set NRF_LOG_DEFERRED to 0 in sdk_config.h ?

[zxcv7063]

Hi:

   1, radio_callback() unused TIMER2,It is not only TIMER2 cannot enter callback, And PPI doesn't start.

the follow code snippet:

     

   2. Yes!  when exit radio_callback(),It can start to print.

   3.Try to set NRF_LOG_DEFERRED to 0 in sdk_config.h, The result is the same. Has nothing to do with it.

[Sigurd]

zxcv7063 said:

2. Yes!  when exit radio_callback(),It can start to print.

While you are inside the radio_callback() / signal handler, you won't be able to process any interrupt before you exit the signal handler, since the signal handler runs at the highest priority. See this link