2 GPIOTE Interrupts, Only one of the handler functions being hit

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Sigurd — Wed, 09 Aug 2017 13:01:52 GMT

If INT signal is high before the gpiote is set-up, the interrupt will never trigger because there is no transition from low to high after the gpiote is enabled.

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Wael — Tue, 08 Aug 2017 21:09:26 GMT

Well, I finally brought the scope to my desk so that I can see the INT signal on the scope while I'm debugging. Come to find out, the interrupt does not get triggered during debug mode BUT DOES work when I flash the device and do not run in debug mode. I am using Keil version 5.23 and can not figure out why this is happening. During Debugging, the INT2(Pcap) IC handler does get hit.

This is what I'm seeing when I Debug:

Erase the Flash
repower the device (the INT1 signal is low as expected)
press the Debug button while the program is downloading, I can see the INT signal on the scope until the program breaks at the first line in the main function. (the signal stays high)
press the Go button( the signal stays high) and the breakpoint in the handler is never hit)

Any help would e greatly appreciated.

Regards,

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Sigurd — Tue, 08 Aug 2017 12:08:04 GMT

No, the function names can be different, i.e. you can use both in_pin_handler and IMU_INT1_pin_handler. I have tried reproducing the issue using SDK 11, but I’m not seeing any problems here. Please make sure that the IMU is connect to the correct nRF-pin(IMU_INT1_PIN). Did you try debug mode? Exactly how are you checking if the interrupt is triggered?

Also make sure that nothing is reconfiguring the pin later in you program. i.e. check that GPIOTE register and GPIO P0 register are correct.

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Wael — Mon, 07 Aug 2017 20:21:59 GMT

11, yes I am using a softdevice/ble. lowering the priority did nothing. I also tested it without the internal pull down and same results. I am going nuts, please help. BTW does the handler function names need to be the same for both INTs?

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Sigurd — Mon, 07 Aug 2017 14:09:44 GMT

What SDK version are you using ? Are you using the SoftDevice/BLE? Try lowering the GPIOTE_CONFIG_IRQ_PRIORITY in sdk_config.h, to e.g. to 3. If you are using SDK 11 or lower use nrf_drv_config.h instead of sdk_config.h. You can also test it without the internal pulldown, and see if that helps. Note that the pin need to reach voltage of 0.7 * Vdd to be detected as "high".

Also make sure that you are not running into any error-handlers, see here on how to debug.

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Wael — Mon, 07 Aug 2017 13:14:42 GMT

Hello:

Thanks for your reply. I have checked the IMU_INT1_PIN with a oscilloscope and it functions as it should. Is it possible the issue is I have 2 different handler names for the different IRQs?

RE: 2 GPIOTE Interrupts, Only one of the handler functions being hit

Sigurd — Mon, 07 Aug 2017 12:52:21 GMT

Hi,

I don't see anything wrong with the code you posted. Note that you have pulldown on IMU_INT1_PIN, but not on CDC_INT_PIN. When CDC_INT_PIN goes from high to low, the in_pin_handler should be triggered and when IMU_INT1_PIN goes from low to high IMU_INT1_pin_handler should be triggered.

You should check with a oscilloscope/logic analyzer that the IMU_INT1_PIN pin actually goes high, if not the interrupt will of course not be triggered.