GPIOTE interrupt not working with softdevice s130

[Denver]

I am using the template example for S130(works fine). I tried adding a simple Pin interrupt on the code but it didn't call the pin interrupt handler everytime I press the button. I believe I'm using some part of the peripherals that are restricted in S130. Below is my code, I put it before all the BLE initialization.

---

err_code = nrf_drv_gpiote_init();

APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(true);

in_config.pull = NRF_GPIO_PIN_PULLDOWN;

err_code = nrf_drv_gpiote_in_init(BUTTON_1, &in_config, in_pin_handler);

APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(BUTTON_1, true);

Am I missing something? or Is this implementation not applicable with Softdevices. BTW the code for interrupt works if no support of BLE is added.

[Petter Myhre]

Which SDK and SoftDevice version are you using?

[Denver]

hi Petter, I am using SDK 14 and Softdevice S130. I manage to make the pin Interrupt works by using a different routine. Maybe right now, I want to understand why this code is not working.

[Denver]

So I manage to solve my problem but using a different routine. Still please help me to understand further why the above code is not working. Anyway, below code is what I used to work with Pin Interrupt together with Softdevices.

Update: Now, bot codes are working just by changing PULLDOWN to PULLUP.

//Initialization uint32_t err_code;

APP_GPIOTE_INIT(APP_GPIOTE_MAX_USERS); // APP_GPIOTE_MAX_USERS = 1 static app_button_cfg_t p_button[] = {{BUTTON_1, APP_BUTTON_ACTIVE_LOW, NRF_GPIO_PIN_PULLUP, in_pin_handler}};

// Initializing the buttons. err_code = app_button_init (p_button, sizeof(p_button) / sizeof(p_button[0]), 10); APP_ERROR_CHECK(err_code);

// Enabling the buttons. err_code = app_button_enable(); APP_ERROR_CHECK(err_code);

[KPK]

I noticed that with the new routine you are initialising your button with a Pull up configuration whereas in the previous routine it was pull down. Was it intentional? Have you tried using your first routine with a pull up configuration?

I had a look at the design files for PCA10040 board (assuming you use them) and the buttons are connected to ground already. If you use them in Pull down mode, the state never toggles and so no interrupt is generated.

[Denver]

Hi KPK, what I did just now is to change my current code from PULLUP to PULLDOWN. Now my code is not working. I bet this solve the issue. I will try to use the previous routine if it will fix the problem. Thank you KPK