NRF_DELAY_MS blocks interrupt

[Newbie]

Hello,

I am using sdk12,2.2 and nrf52832. I have interfaced bme680 sensor with nrf52. I am facing strange challenge.

My button interrupt is working every time but it stops when my firmware is executing nrf_delay_ms api. It again responds when nrf_delay_ms has been completed.

Thanks,

[AmbystomaLabs]

nrf_delay should be used basically never.  I think they put it in there to keep people happy who still remember basic.

The nrf_delay operates by executing a series of __nop (ie, no operation opcode). Since this just hangs up the processor during the delay it won't service your interrupt depending on the interrupt priority.

[AmbystomaLabs]

And, since you will likely ask, "how should I do a delay then???"

The simplest and best method for long several millisecond or more delays is the app_timer.

Here is a recent discussion, also there are numerous tutorials on it: https://devzone.nordicsemi.com/f/nordic-q-a/34551/nrf51822-app-timer/132548#132548

If you are using the delay because you are trying to bit bang your bme sensor, then you might have more luck learning about the main HF CLK based timers or for low speed stuff then use the RTC based timers.

[Senchoi]

Do you mean that using nrf_delay in rtc_handler or timer handler will temporarily stop timer or rtc counting up?

[Jørgen Holmefjord]

Senchoi said:

Do you mean that using nrf_delay in rtc_handler or timer handler will temporarily stop timer or rtc counting up?

No, the RTC and TIMER peripherals are HW peripherals. They will keep running regardless of what the CPU does, until they are stopped.

nrf_delay will only stall the CPU, causing higher current consumption (CPU running), and preventing CPU from performing other tasks.