GPIO Interrupt not triggered

RE: GPIO Interrupt not triggered

Hieu — Thu, 30 Jun 2016 07:51:36 GMT

@Kristin: Ah, that is exactly what I have been doing. Thanks for the help, Kristin and Petter

RE: GPIO Interrupt not triggered

FormerMember — Wed, 29 Jun 2016 16:42:33 GMT

The easiest way is to just change the number of buttons and LEDs defined in pca10028.h.

If you want to keep pca10028.h unmodified, you can do the following:

Copy pca10028.h and create a new pca10028 board file: my_board.h
Change the number of buttons/LEDs.
In the top of my_board.h, change the define to f.ex:

#ifndef MY_BOARD_H #define MY_BOARD_H
Add my_board.h to the list of boards in boards.h (named f.ex: BOARD_MY_BOARD)
In project ->options for target -> C/C++ -> "define": replace BOARD_PCA10028 with BOARD_MY_BOARD

RE: GPIO Interrupt not triggered

Hieu — Wed, 29 Jun 2016 04:01:29 GMT

@kristin: I understood that I could simply remove BSP. However, what I am asking is for quick test, is there a way for me to override just 1-2 buttons and 1-2 LED that the BSP controls, without having to configure BSP again.

I figured one of the thing I could do is create a template project where it includes a modified pca10028.h that only make use of 2 LED and 2 Button. Yet if there is a better way I am interested in learning.

RE: GPIO Interrupt not triggered

FormerMember — Fri, 24 Jun 2016 11:13:58 GMT

The example provided in this thread replaces the BSP module by GPIOTE events directly.

RE: GPIO Interrupt not triggered

FormerMember — Fri, 24 Jun 2016 11:12:04 GMT

Yes, you can choose to not include the BSP module in your project.

RE: GPIO Interrupt not triggered

Hieu — Fri, 24 Jun 2016 04:10:14 GMT

My sincere apology, Petter. I was tangled up with a lot of deadline soon after our last discussion, and replying to you slipped out of my mind.

What I meant by overwriting the button behavior is replacing the behavior bsp_init() programmed with my own.

RE: GPIO Interrupt not triggered

Petter Myhre — Thu, 19 May 2016 14:07:14 GMT

Yes. It should be pulled up. Overwrite the button behavior? I don't quite understand.

RE: GPIO Interrupt not triggered

Hieu — Thu, 19 May 2016 09:20:57 GMT

*update: fixed that extreme sensitivity issue. Turns out I should have the GPIO pin being pulled up, so I did just that.

So my new question would be, is it impossible to overwrite the button behavior set by bsp_init()?

RE: GPIO Interrupt not triggered

Hieu — Thu, 19 May 2016 09:18:03 GMT

Also, my application is based off of the ble_app_uart example so during setup it also call:

uint32_t err_code = bsp_init(BSP_INIT_LED /* | BSP_INIT_BUTTONS */,
                                 APP_TIMER_TICKS(100, APP_TIMER_PRESCALER), 
                                 bsp_event_handler);

Perhaps this matters? I tried remove | BSP_INIT_BUTTON from the parameter and managed to make the button works somehow. However, it seems the button is extremely sensitive, just my hand touching it causes LED 4 to blink rapidly.

RE: GPIO Interrupt not triggered

Hieu — Thu, 19 May 2016 09:10:40 GMT

Hi Petter,

Sorry for being late with the follow up. I just got out of a very tight deadline rush.

I have tried explicitly calling the function nrf_drv_gpiote_init() as you shown in your code. However that does not help. It returns NRF_ERROR_INVALID_STATE indicating that GPIOTE has already been initialized by something else.

RE: GPIO Interrupt not triggered

Hieu — Thu, 05 May 2016 02:26:20 GMT

Hi Petter, I indeed missed that function call. However it is coincidentally covered when I called app_pwm_init() at an earlier point in my application, so it does not seem to be the problem.

I have however added the call into my button4_config() as instructed in the GPIOTE driver page, however the button interrupt is still not called.

RE: GPIO Interrupt not triggered

Petter Myhre — Wed, 04 May 2016 11:48:58 GMT

I can't see that you are calling nrf_drv_gpiote_init() anywhere

Edit 1: Try this:

void button_interrupt_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    nrf_gpio_pin_toggle(LED_4);
}

static void button4_config()
{
    nrf_drv_gpiote_in_config_t config;
    memset(&config, 0, sizeof(nrf_drv_gpiote_in_config_t));
    config.sense = NRF_GPIOTE_POLARITY_HITOLO;
    config.pull = NRF_GPIO_PIN_PULLUP;
    config.hi_accuracy = false;
    config.is_watcher = false;

    nrf_drv_gpiote_in_init(BUTTON_4, &config, button_interrupt_handler);
    nrf_drv_gpiote_in_event_enable(BUTTON_4, true);

}

/**
 * @brief Function for application main entry.
 */
int main(void)
{
    ret_code_t err_code;

    nrf_gpio_cfg_output(LED_4);
        
    err_code = nrf_drv_gpiote_init();
    APP_ERROR_CHECK(err_code);

    button4_config();

    while (true)
    {
    }
}