How to redefine PPI tasks inside a TIMER interrupt ???

RE: How to redefine PPI tasks inside a TIMER interrupt ???

Ole Morten — Tue, 13 Aug 2013 06:47:31 GMT

This doesn't seem very related to the original question here, but this is a file the application should provide when using the TWI modules from the SDK. An example can be found in this folder: Board\nrf6310\nRF6350_radio_configuration_example

RE: How to redefine PPI tasks inside a TIMER interrupt ???

oscalcmen — Tue, 13 Aug 2013 02:13:19 GMT

where is located the twi_master_config.h header file?

RE: How to redefine PPI tasks inside a TIMER interrupt ???

Sébastien Despont — Mon, 12 Aug 2013 11:58:01 GMT

Thank you so much. I was stucked on this problem for 2 days.

RE: How to redefine PPI tasks inside a TIMER interrupt ???

Ole Morten — Mon, 12 Aug 2013 11:49:37 GMT

If you see this consistently failing (with a HardFault error), the timer interrupt most likely runs with too high priority to call softdevice functions. The problem with this is described in the "Application Programming Interface" section in the nRF51 Series Reference Manual appendix:

SVC calls are conceptually software triggered interrupts with a procedure call standard for parameter passing and return values. Each API call generates an interrupt allowing single-thread API context and SoftDevice function locations to be independent from the application perspective at compile-time. SoftDevice API functions can only be called from lower interrupt priority when compared to the SVC priority. See the Exception (interrupt) management with a SoftDevice section on page 182.

The SVC interrupt have priority 2, so to call softdevice API functions (for example the PPI function), your IRQ handler must run at priority 3.