nrfx_gpiote same pin register more than GPIOTE control?

[odin huang]

I take the external PWM signal, I directly used the method of controlling the GPIOTE register to be successful. 

But I can't achieve the same effect using the program in the standard SDK.

An error occurs when I declare using the standard SDK. Is there a way to program using the standard SDK? 

PS: SDK version: nRF 16.0.0

there is successful

    NRF_GPIOTE->CONFIG[PWM_INPUT_GPIOTE_RISE_EDGE_CH] = GPIOTE_CONFIG_MODE_Event << GPIOTE_CONFIG_MODE_Pos | 
                                         GPIOTE_CONFIG_POLARITY_LoToHi << GPIOTE_CONFIG_POLARITY_Pos | 
                                         pin_number << GPIOTE_CONFIG_PSEL_Pos | 
                                         GPIOTE_CONFIG_OUTINIT_Low << GPIOTE_CONFIG_OUTINIT_Pos;    // ignored when gpio is set to event mode

    NRF_GPIOTE->CONFIG[PWM_INPUT_GPIOTE_FALL_EDGE_CH] = GPIOTE_CONFIG_MODE_Event << GPIOTE_CONFIG_MODE_Pos | 
                                         GPIOTE_CONFIG_POLARITY_HiToLo << GPIOTE_CONFIG_POLARITY_Pos | 
                                         pin_number << GPIOTE_CONFIG_PSEL_Pos | 
                                         GPIOTE_CONFIG_OUTINIT_High << GPIOTE_CONFIG_OUTINIT_Pos;    // ignored when gpio is set to event mode

there is failure

    err_code = nrfx_gpiote_in_init(pin_number, &gpiote_LoToHi_cfg, PWM_emtpy_handler); //Low to High edge
    APP_ERROR_CHECK(err_code);

    err_code = nrfx_gpiote_in_init(pin_number, &gpiote_HiToLo_cfg, PWM_emtpy_handler); //High to low edge
    APP_ERROR_CHECK(err_code);

[Heidi-Irene Harvey Sollie]

Hi!

What error message are you seeing when it fails?

Best regards,

Heidi

[odin huang]

trace nrfx_gpiote_in_init

/* Only one GPIOTE channel can be assigned to one physical pin. */
if (pin_in_use_by_gpiote(pin))
{
err_code = NRFX_ERROR_INVALID_STATE;
}

^^^^^

Is this limiting GPIOTE to only one physical pin?

But when I use the register layer myself, I can operate normally.

PS: pin_number is same

[Heidi-Irene Harvey Sollie]

Hi!

You can't initialize the same pin twice, the nrfx_gpiote_in_init function checks if the pin_number is already initialized and returns an error. However, when you write directly to the registers, you just overwrite whatever was there from before without getting an error code.

This is why the first example "succeeds" while the second fails. I put succeeds in quotation marks because you are just overwriting the initial command, not executing both.

If what you want to do is set the pin to toggle mode, and then get an interrupt every time the pin changes state I would suggest something like 

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(true);
in_config.pull = NRF_GPIO_PIN_PULLUP;

err_code = nrf_drv_gpiote_in_init(PIN_IN, &in_config, in_pin_handler);
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(PIN_IN, true); 

Best regards,

Heidi

[odin huang]

Hi,

Thank you for your answer. My usage scenario is to use GPIOTE and PPI to trigger TIMER in conjunction with TIMER. But the functions in nrf_gpiote.c on the SDK cannot meet my usage purpose, because I need to reduce unnecessary interrupts.

Heidi-Irene Harvey Sollie said:

overwriting