Are SPI interrupt disabled in GPIOTE handler?

RE: Are SPI interrupt disabled in GPIOTE handler?

Jørgen Holmefjord — Tue, 12 Sep 2017 11:43:36 GMT

You should not set the IRQ priority to the ones reserved by the softdevice. The assert checking this might not be implemented unless DEBUG_NRF or DEBUG_NRF_USER is defined in the preprocessor symbols. Try setting the priority of the GPIOTE handler to 3 and priority of SPI to 1 instead.

RE: Are SPI interrupt disabled in GPIOTE handler?

Prasad — Tue, 12 Sep 2017 06:55:04 GMT

Yes, I did set the priority with softdevice present.

RE: Are SPI interrupt disabled in GPIOTE handler?

Jørgen Holmefjord — Mon, 11 Sep 2017 14:32:17 GMT

You should get an assert if you set the priority to one of the ones reserved for the softdevice, and SOFTDEVICE_PRESENT is defined. Did you set this priority with softdevice present?

RE: Are SPI interrupt disabled in GPIOTE handler?

Prasad — Mon, 11 Sep 2017 14:03:24 GMT

Thanks Jørgen, the issue got resolved when I changed SPI_DEFAULT_CONFIG_IRQ_PRIORITY in sdk_config.h from 3 to 2. But I found this comment in sdk_config.h.

// <i> Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 

#ifndef SPI_DEFAULT_CONFIG_IRQ_PRIORITY
#define SPI_DEFAULT_CONFIG_IRQ_PRIORITY 2
#endif

Does this mean that I cannot call softdevice APIs from the SPI event handler now?

RE: Are SPI interrupt disabled in GPIOTE handler?

Prasad — Mon, 11 Sep 2017 13:40:04 GMT

I am using NRF_DRV_SPI_DEFAULT_CONFIG to initialise my SPI instance and I have set SPI_DEFAULT_CONFIG_IRQ_PRIORITY 3 in sdk_config.h I guess I need to change this and check again...

RE: Are SPI interrupt disabled in GPIOTE handler?

Jørgen Holmefjord — Mon, 11 Sep 2017 10:42:29 GMT

What is the IRQ priority configured for the SPI master driver? Notice the comment from the SPI driver doucmentation: "There is no context blocking in the interrupt handler. Therefore, it is assumed that the driver API will not be called from a context with higher priority than the instance interrupt, because this might cause driver failure.". If SPI driver priority is set to APP_IRQ_PRIORITY_LOWEST, you might see issues like this.