Migration to SDK15.1: NRFX GPIOTE IN EVENT

RE: Migration to SDK15.1: NRFX GPIOTE IN EVENT

Paweł — Thu, 30 Aug 2018 18:30:54 GMT

I managed it. It turned out that I mistook some libraries - in many cases there are few locations for libraries with same names. I gave paths to wrong headers and it caused that program was baing compiled but tasks from GPIOTE did not work at all.

RE: Migration to SDK15.1: NRFX GPIOTE IN EVENT

Paweł — Tue, 28 Aug 2018 20:56:52 GMT

I just pasted my functions to the example project (pin_change_int_pca_10056) and everything is ok. I do not understand what I have forgotten to configure in my own blank project. Is there any CPU/CLOCK or anything to configure to run IN EVENTS? I did not mention that I work with Segger Embedded Studio. Maybe I forgot something with IDE configuration?

I am sorry if I am not precise enough, if yoy need more informations or files to be included, just say, please. I feel confused because cannot find any differences in configurations of example and mine.

RE: Migration to SDK15.1: NRFX GPIOTE IN EVENT

Paweł — Tue, 28 Aug 2018 18:44:40 GMT

Thank you for your fast response. Unfortunately, the code behaves as before. I included banch of libraries but there is no difference. I used also unchanged sdk_config.h.

I guess that I do not define something and this cause the problems even though program compiles. Could you please describe what is indispensible to make the program work on nrfx drivers? I mainly mean every needed defines because as I see the code is rather error-free?

RE: Migration to SDK15.1: NRFX GPIOTE IN EVENT

Vidar Berg — Tue, 28 Aug 2018 12:18:10 GMT

Hi,

Please insert the code below into your project and check if it works. You can change LED_4 and BUTTON_1 to match the pinout of your board.

#include <stdbool.h>
#include <stdint.h>
#include "nrf.h"
#include "nrf_gpiote.h"
#include "nrf_gpio.h"
#include "boards.h"
#include "nrf_drv_gpiote.h"
#include "app_error.h"


void gpiote_callback(nrfx_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    if (pin == BUTTON_1)
    {
        nrfx_gpiote_out_task_trigger(LED_4); //toggle output on button press - can be done through PPI
    }
}


void gpiote_init()
{
    uint32_t                 err_code;
    nrfx_gpiote_out_config_t config_out = NRFX_GPIOTE_CONFIG_OUT_TASK_TOGGLE(true);
    nrfx_gpiote_in_config_t  config_in = NRFX_GPIOTE_CONFIG_IN_SENSE_HITOLO(true);

    config_in.pull = NRF_GPIO_PIN_PULLUP;

    err_code = nrfx_gpiote_init();
    APP_ERROR_CHECK(err_code);
    
    err_code = nrfx_gpiote_out_init(LED_4, &config_out);
    APP_ERROR_CHECK(err_code);

    nrfx_gpiote_out_task_enable(LED_4);

    err_code = nrfx_gpiote_in_init(BUTTON_1, &config_in, gpiote_callback);
    APP_ERROR_CHECK(err_code);

    nrfx_gpiote_in_event_enable(BUTTON_1, true);
    
}

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


    while (true)
    {
        // Do Nothing - GPIO can be toggled without software intervention.
    }
}