app_timer value affects twim?

[Raymond Pelletier]

I'm seeing an odd behavior where the ability for our application to communicate to peripherals via twim is being affected by the initialization values for app timers.

Timers are initialized and started before twim.

• a single shot timer with duration 20 seconds
• a repeated timer with duration 1 seconds
• a repeated timer with duration of 25 milliSeconds

After setting up GPIO and the softdevice I initialize and enable TWIM

The application works fine until I increase the duration of the third timer from 25 milliSeconds to 100 millSeconds.

At 100 milliSeconds TWIM no longer works.

Can anyone posit a theory as to why this is the case?

I've not been able to confirm whether or not the pin we use for I2C_SCL has a clock signal or not. I'm primarily a software person so my hardware diagnostic skills are pretty basic.

[Raymond Pelletier]

Changing the initialization order fixes the problem.  Softdevice > timers > TWIM. Works for all values of the timer. If anyone has an explanation of why the original order fails, if one exists, it would be useful to clarify and avoid issues going forward.