nrf9160 interrupts {

RE: nrf9160 interrupts {

Håkon Alseth — Tue, 02 Jun 2020 12:52:06 GMT

Hi,

[quote user="ephraim"]Where can I find the document of how to set the priority GPTIOE 49,0 ?.[/quote]

The description in dts is available, but not the usage of the magic number corresponding to the NVIC IRQn number:

https://github.com/zephyrproject-rtos/zephyr/blob/master/dts/bindings/interrupt-controller/arm%2Cv8m-nvic.yaml

I have opened up a discussion with the developers on how this can be made easier. This vector-number corresponds to the GPIOTE_IRQn define. For nRF9160, in non-secure mode, it is this one:

https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/mdk/nrf9160.h#L113

Note that this number will be different if you run on nRF52832, 840, etc. Then you have to manually check the "IRQn_Type" number for that specific device.

I'll be sure to bring this tedious configuration up with the developers, and see if we can get a better solution in the future.

Kind regards,

Håkon

RE: nrf9160 interrupts {

ephraim — Sun, 31 May 2020 06:35:34 GMT

Hi.

It works , Many thanks

One more question before I close this post .

Where can I find the document of how to set the priority GPTIOE 49,0 ?.

RE: nrf9160 interrupts {

Håkon Alseth — Wed, 27 May 2020 13:32:02 GMT

Hi,

[quote user=""]k_timer_init(&my_timer, my_expiry_function, NULL);[/quote]

This will run in interrupt priority, which is inherited from the kernel timer instance RTC1, which is hardcoded with this priority:

https://github.com/nrfconnect/sdk-zephyr/blob/master/drivers/timer/nrf_rtc_timer.c#L102

I wouldn't recommend changing this.

[quote user=""]How can I set the external interrupt to have higher priority than the timer interrupt ?.[/quote]

GPIOTE needs to have a higher priority than RTC1, which has '1', so you'll need GPIOTE prio to '0'.

This can be done by creating a $board_name.overlay file (nrf9160_pca10090ns.overlay if using ncs tag v1.2.0, nrf9160dk_nrf9160ns.overlay on current master) holding your configuration:

&gpiote {
    status = "okay";
    interrupts = <49 0>;
};

I tested the above with the zephyr/samples/basic/button, where I added this to the button callback:

void button_pressed(struct device *gpiob, struct gpio_callback *cb,
		    u32_t pins)
{
	printk("Button pressed at %" PRIu32 "\n", k_cycle_get_32());
	printk("GPIOTE ISR Prio: %d\n", NVIC_GetPriority(GPIOTE1_IRQn));
	printk("RTC1 ISR Prio: %d\n", NVIC_GetPriority(RTC1_IRQn));
}

And it now prints this:

Button pressed at 26472
GPIOTE ISR Prio: 1
RTC1 ISR Prio: 2

A side note: In DTS, the number is offset by '1' compared to what is read out from the NVIC (NVIC_GetPriority(...)). 0 in DTS -> 1 when you read NVIC directly.

Could you try this and see if it works better?

You can also consider to use a system workqueue when handling larger non-timing critical logic in interrupt handlers.

Kind regards,

Håkon