about GPIOTE event

RE: about GPIOTE event

Hansome — Tue, 13 Aug 2019 06:35:17 GMT

Thanks!

RE: about GPIOTE event

ovrebekk — Tue, 13 Aug 2019 06:26:21 GMT

If you want to call a SoftDevice function (any function with the sd_ prefix), or an SDK function that calls into the SoftDevice under the hood, you have to be in interrupt priorty 6, 7, or in thread context.

The GPIOTE driver should not need to call any SoftDevice functions, so it should be safe to run at interrupt priorities 2 and 3 also.

Best regards
Torbjørn

RE: about GPIOTE event

Hansome — Mon, 12 Aug 2019 12:47:19 GMT

So as shown in the figure, I'm a little confused,

RE: about GPIOTE event

ovrebekk — Mon, 12 Aug 2019 11:48:46 GMT

No, priorities 2, 3, 6, and 7 are available when using the SoftDevice.

Best regards
Torbjørn

RE: about GPIOTE event

Hansome — Mon, 12 Aug 2019 10:32:55 GMT

Setting GPIOTE_CONFIG_IRQ_PRIORITY = 2 will affect the softdevice?

RE: about GPIOTE event

ovrebekk — Mon, 12 Aug 2019 07:20:36 GMT

You should be able to set the GPIOTE interrupt priority by changing the GPIOTE_CONFIG_IRQ_PRIORITY define in sdk_config.h. By default it is set to 6, which is the same as the UART interrupt priority.

Maybe you can try setting it to 2 or 3 and see if it works better?

Best regards
Torbjørn

RE: about GPIOTE event

Hansome — Sat, 10 Aug 2019 06:30:01 GMT

In addition, what attention should be paid to its interrupt code and how to set its interrupt priority?

RE: about GPIOTE event

Hansome — Sat, 10 Aug 2019 06:05:22 GMT

In addition, How to set GPIOTE interrupt priority?

RE: about GPIOTE event

Hansome — Sat, 10 Aug 2019 03:17:03 GMT

In the UART event handler, only put data to buffer,

static void _on_uart_event(app_uart_evt_t* event)
{

	uint8_t data;
	
	switch(event->evt_type){
		
		case APP_UART_DATA_READY:
			app_uart_get(&data);
			urb_push(data);
			break;

		default:
			break;
		
	}
	
}

On custom hardware

RE: about GPIOTE event

ovrebekk — Fri, 09 Aug 2019 11:32:12 GMT

Are you saying the event won't even happen again if the pulse signal is sent multiple times?

Are you doing a lot of processing in the UART event handler that could delay other interrupts and events?

Are you testing this on custom hardware or on a development kit?

Best regards
Torbjørn

RE: about GPIOTE event

Hansome — Fri, 09 Aug 2019 00:24:18 GMT

Only one pin using GPIOTE,

static void _wakeup_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{

	_pin_flag = true;
	
}

	
void init(void)
{
	
	nrf_drv_gpiote_in_config_t cfg = GPIOTE_CONFIG_IN_SENSE_HITOLO(false);
	
	nrf_drv_gpiote_init();
	cfg.pull = NRF_GPIO_PIN_PULLUP;
	nrf_drv_gpiote_in_init(_WAKEUP_PIN, &cfg, _wakeup_pin_handler);
	nrf_drv_gpiote_in_event_enable(_WAKEUP_PIN, true);

}	
	

void proc(void)
{

	if(_pin_flag){
		wakeup();
		_pin_flag = false;
	}
	
}

RE: about GPIOTE event

ovrebekk — Thu, 08 Aug 2019 13:04:16 GMT

Can you show me the code you use to initialize the GPIOTE callback?

Is this the only pin using GPIOTE, or do you have other pins connected to the GPIOTE, such as buttons?

Best regards
Torbjørn