TIMER1->INTENSET cause a ble connection drop problem.

RE: TIMER1->INTENSET cause a ble connection drop problem.

Susheel Nuguru — Fri, 11 Dec 2015 11:21:42 GMT

No, it cannot be guarenteed (infact, it is not possible) if your PWM signal depends on the interrupt service and while BLE activity. SDK PWM library in SDK uses PPI, TIMERS and GPIOTE to make hardware connections so that its timing does not depend on any ISR.

RE: TIMER1->INTENSET cause a ble connection drop problem.

shadow — Fri, 11 Dec 2015 10:21:14 GMT

Connection drop problem was caused by Unstable LFCLK. After adjust LFCLK(32768), connection drop problem is disappeared But the TIMER2 capture interrupt is missed some time, so It is impossible to make guaranteed 250us ISR for PWM. Is there anyway to make 250us ISR without delay or missing.

Best regards, Joy Kang.

RE: TIMER1->INTENSET cause a ble connection drop problem.

Susheel Nuguru — Fri, 11 Dec 2015 07:21:44 GMT

If you have not set the priority of this IRQ then it is by default running at highest priority which BLE softdevice will not accept. This is because only SD is allowed to used the highest priority interrupts. Set priority of your timer to APP_PRIORITY_LOW or APP_PRIORITY_HIGH. The timing of your PWM signal will be affected with BLE activity as your interrupt execution might be delayed and it depends totally on the BLE activity.