Do I need to change the interrupt priority when using BLE

RE: Do I need to change the interrupt priority when using BLE

Yogesh — Mon, 16 Jan 2017 09:19:35 GMT

Thanks a lot Sigurd

RE: Do I need to change the interrupt priority when using BLE

Sigurd — Mon, 16 Jan 2017 08:11:33 GMT

Yes, SYSTICK will work if you don't place the CPU in sleep mode. But, this is NOT recommended. The CPU will then be on all the time, using 3.7mA.If you use a typical coin-cell battery, the battery will be empty in 1-2 days.

RE: Do I need to change the interrupt priority when using BLE

Yogesh — Mon, 16 Jan 2017 06:13:15 GMT

also i am using SPI0 interrupt.What precautions do i need to be taken? I am waiting for the reply.

RE: Do I need to change the interrupt priority when using BLE

Yogesh — Fri, 13 Jan 2017 14:23:20 GMT

Thanks . If i comment down the power_manage(); will systick work?

RE: Do I need to change the interrupt priority when using BLE

RK — Fri, 13 Jan 2017 13:34:20 GMT

Yes SYSTICK is turned off when the device sleeps, so it's not that useful. Is there a reason you put multiple question marks after each question????????????????????????

RE: Do I need to change the interrupt priority when using BLE

Sigurd — Fri, 13 Jan 2017 13:34:18 GMT

In the SDK BLE examples the GPIOTE priority is usually set to 7. If you don’t set the correct priority you will typically get an assert/error. The CPU is placed in sleep mode to save power between events/interrupts, and the CPU clock is therefore turned off. The nRF52 implementation of systick uses the CPU clock, so systick won’t return any interrupts when the CPU is in sleep/low-power mode.

RE: Do I need to change the interrupt priority when using BLE

Yogesh — Fri, 13 Jan 2017 13:00:24 GMT

HI,

Thanks for the reply. I am able to change the priorities of both systick interrupt, GPIOTE interrupt to 7 and 6 repectively. also I could change the Timer0 to Timer 1. I didnt understand why i cant use Systick??why source clock gets turned off???would you please elaborate??

RE: Do I need to change the interrupt priority when using BLE

Sigurd — Fri, 13 Jan 2017 12:10:00 GMT

Hi,

Interrupt priorities 0,1,4 and 5 are reserved for the SoftDevice. Your application can use priorities 2,3,6 and 7. The SoftDevice also uses TIMER0, so you will need to switch to TIMER1. Systick is sourced by the same clock as the CPU, which is turned off when going to sleep(WFE/WFI), so I recommend that you look into using the app_timer instead.