GPIOTE event not coming

RE: GPIOTE event not coming

Vidar Berg — Mon, 17 Aug 2020 06:21:12 GMT

You need to set the INTENSET register to enable wakeup as Dmitry has pointed out. Otherwise, the GPIOTE event register is not going to be connected to anything (see Peripheral interface). You also need to enable SEVONPEND and mask the interrupt if you really need to trigger wakeup without servicing an ISR.

RE: GPIOTE event not coming

Surya — Mon, 10 Aug 2020 05:00:10 GMT

no, my case is different. anybody tried my code in nrf52832 board?

RE: GPIOTE event not coming

Dmitry — Thu, 06 Aug 2020 08:09:36 GMT

Maybe this topic will be helpful.

RE: GPIOTE event not coming

Surya — Mon, 03 Aug 2020 05:35:52 GMT

I added the above mention line of code in gpio_init(), but no use. I am not getting any events when I press a button in the system on mode.

RE: GPIOTE event not coming

Dmitry — Sat, 01 Aug 2020 19:54:34 GMT

[quote userid="71007" url="~/f/nordic-q-a/63944/gpiote-event-not-coming/262632"]the same sequence is being used in all examples. [/quote]

The sev/wfe/wfe sequence saves some power when waiting for interrupt, but in case of waiting-for-event loop, you will lose an event if it comes while CPU is active.

I forgot to mention that SEVONPEND flag should be enabled to wake up on any events, including ones disabled in NVIC:

SCB->SCR |= SCB_SCR_SEVONPEND_Msk;

I played with such method for bit-banging protocol some time ago and found it unreliable (sometimes device didn't wake up when it should). For button handling, I don't see any advantage over traditional interrupt-based method.

RE: GPIOTE event not coming

Surya — Sat, 01 Aug 2020 04:50:10 GMT

the same sequence is being used in all examples. anyway I checked with the order you mentioned but it is not waiting for an event, immediately going to gpio_check() again.

RE: GPIOTE event not coming

Dmitry — Fri, 31 Jul 2020 13:56:56 GMT

__SEV();
__WFE();
__WFE();

it seems should be different order: __WFE(); __SEV(); __WFE();

RE: GPIOTE event not coming

Surya — Fri, 31 Jul 2020 13:06:09 GMT

i added below lin of code

NRF_GPIOTE->INTENSET = GPIOTE_INTENSET_PORT_Set << GPIOTE_INTENSET_PORT_Pos;

to gpio_init() but still event is not coming.

RE: GPIOTE event not coming

Dmitry — Fri, 31 Jul 2020 11:21:38 GMT

Yes, PORT interrupt should be enabled in NRF_GPIOTE->INTENSET to wake up on that event. If you don't want to use an interrupt, just don't enable it in NVIC.

RE: GPIOTE event not coming

Jared — Fri, 31 Jul 2020 08:48:18 GMT

[quote user="Surya"]GPIOTE event will be generated when I press a button (as per my configuration) and is working if I goto system_off mode. but when the system is on, the GPIOTE event is not coming. do you mean to say GPIOTE events will not come in system_on condition?[/quote]

no, that's not what I meant. I can see that your program does somewhat what you intended it to do. But there is a better way to make nRF do something based on what button that is pressed ( See the BSP example).

[quote user="Surya"] do you mean to say GPIOTE events will not come in system_on condition?[/quote]

From the product specification:

"PORT is an event that can be generated from multiple input pins using the GPIO DETECT signal.

The event will be generated on the rising edge of the DETECT signal. See GPIO — General purpose input/output for more information about the DETECT signal.

Putting the system into System ON IDLE while DETECT is high will not cause DETECT to wake the system up again. Make sure to clear all DETECT sources before entering sleep. If the LATCH register is used as a source, if any bit in LATCH is still high after clearing all or part of the register (for instance due to one of the PINx.DETECT signal still high), a new rising edge will be generated on DETECT, see Pin configuration.

Trying to put the system to System OFF while DETECT is high will cause a wakeup from System OFF reset.

This feature is always enabled although the peripheral itself appears to be IDLE, that is, no clocks or other power intensive infrastructure have to be requested to keep this feature enabled. This feature can therefore be used to wake up the CPU from a WFI or WFE type sleep in System ON with all peripherals and the CPU idle, that is, lowest power consumption in System ON mode.

In order to prevent spurious interrupts from the PORT event while configuring the sources, the user shall first disable interrupts on the PORT event (through INTENCLR.PORT), then configure the sources (PIN_CNF[n].SENSE), clear any potential event that could have occurred during configuration (write '1' to EVENTS_PORT), and finally enable interrupts (through INTENSET.PORT)".

The interrupt has to be enabled for it to work.

RE: GPIOTE event not coming

Surya — Fri, 31 Jul 2020 07:51:54 GMT

hi Jared,

I don't understand "This is surely not the intended way of using the GPIOTE peripheral. "

GPIOTE event will be generated when I press a button (as per my configuration) and is working if I goto system_off mode. but when the system is on, the GPIOTE event is not coming. do you mean to say GPIOTE events will not come in system_on condition?

GPIOTE will only work to wakeup system from off?

RE: GPIOTE event not coming

Jared — Thu, 30 Jul 2020 13:56:54 GMT

Hi.

This is surely not the intended way of using the GPIOTE peripheral. The whole idea of GPIOTE is to automatically do tasks based on events without involving the CPU. I suggest looking at the BSP example, it does somewhat what you're trying to do and implements IDLE sleep.

regards

Jared

RE: GPIOTE event not coming

Surya — Thu, 30 Jul 2020 05:08:49 GMT

thanks for your reply.

I have provided a simple code. in that, I enabled 4 GPIOTE events.

if i am going to systemoff instead of waiting in low power mode NRF52832 is waking up.

Q1.can GPIOTE events cant make NRF52832 come out of low power mode?

Q2. GPIOTE events won't come when system_on condition?

RE: GPIOTE event not coming

Jared — Wed, 29 Jul 2020 13:16:43 GMT

[quote user=""][/quote]

if i enable GPIOTE IRQ interrupt, i am getting the interrupts in low power mode but I don't want use interrupts.

What do you mean? How does this differ from what you want to achieve? I'm not sure I understand the issue.