Delayed call of Timer Interrupt Handler by one second when Soft Device is in force.

[MichelD]

Soft Device v7.0.1 is used.
Timer instance 2.

I use a "Timer-PPI-ToggleIO" to toggle an output pin to make sure the pin will toggle at the right time.
The timer interrupt is enabled with priority #2 and set from 150 to 250usec. It is variable.
In the interrupt handler the timer value is adjusted.

When Soft Device is not compiled with the firmware, The output pin is toggling nicely.

When the Soft Device is compiled with the firmware, randomly there are gaps of one second.

[Daniel Veilleux]

Hello Michel,

A second is quite a long time. Is that perhaps about how long it takes for your timer to rollover?

If the SoftDevice is enabled and actively doing stuff then it can preempt your code from time to time. However, the possible interruptions are much shorter than a second. I guess the bottom line is: what would happen in your code if your timer interrupt was delayed by a couple hundred microseconds?

[MichelD]

I like that timer rollover mention.

Thanks

[MichelD]

The rollover looks like to be my solution.