RE: How to use sd_nvic_SetPriority with GPIOTE handler on nRF51822

Mike Wirth — Fri, 06 Feb 2015 21:44:32 GMT

Stefan, Thanks for the very informative and complete response. I had already discovered some of what you described by tracing back through gpiote_init() and app_gpiote_init() in the interim. But confirmation of that and the additional info on softdevice interrupts is very useful. (Please consider adding this discussion to future documentation or sample code :-)

Mike

PS: Re soft device interrupts, luckily I can control when my GPIOTE activity occurs and will use the soft device notification feature for radio activity to hold off my use of GPIOTE so that they don't coincide.

RE: How to use sd_nvic_SetPriority with GPIOTE handler on nRF51822

Stefan Birnir Sverrisson — Fri, 06 Feb 2015 12:49:16 GMT

Hi Mike

Since you talk about registering a user I assume you are using the app_gpiote library. In the app_gpiote library, the priority of the GPIOTE interrupt is set to APP_IRQ_PRIORITY_HIGH in order for the library to operate properly. If you open for example the ble_app_bps in nRF51 SDK v6.1.0 you can see that the app_gpiote library is initialized with gpiote_init() in the main function which in turn calls the app_gpiote_init() function in app_gpiote.c. There you can see that the GPIOTE interrupt is set to APP_IRQ_PRIORITY_HIGH. So this interrupt should not be interrupted by other application interrupts since APP_IRQ_PRIORITY_HIGH is the highest application priority interrupt. Only softdevice interrupts have higher priority. More on how softdevice interrupts affects the GPIOTE interrupt can be found on this thread and this thread

Because the app_gpiote.c does not use the sd_* functions to set the GPIOTE priority (uses NVIC_*) you must call gpiote_init() before initializing the softdevice with ble_stack_init(). You should not attempt to change the priority dynamically, only set it during initialization.