RE: NRF52832 Long GPIOTE Interrupt Delay - s132

boraciner — Tue, 25 Aug 2020 20:11:38 GMT

I realized that when I read gpio in a while true loop I'm getting much much better results. So MCU is going into sleep mode .. now I will try to block it go into sleep

RE: NRF52832 Long GPIOTE Interrupt Delay - s132

boraciner — Tue, 25 Aug 2020 19:27:38 GMT

Thanks for your reply but actually I will process SDA SCL lines while listening to them via interrupts. PPI cannot help me because I will not try to toggle a led. Is there any other way to do it?

RE: NRF52832 Long GPIOTE Interrupt Delay - s132

Jared — Tue, 25 Aug 2020 12:03:02 GMT

Hi,

I suggest using the GPIOTE + PPI directly instead as this offloads the CPU and is much faster than doing it purely based on event handlers in SW. Try something like this for setting the pin on a Low to high transition:

static void gpiote_setup(void)
{
    uint32_t in_evt_addr;
    uint32_t gpiote_task_addr;
    nrf_ppi_channel_t ppi_channel;
    ret_code_t err_code;

    nrf_drv_gpiote_out_config_t config_out = GPIOTE_CONFIG_OUT_TASK_TOGGLE(true);
    nrf_drv_gpiote_in_config_t  config_in = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);

    err_code = nrf_drv_gpiote_out_init(GPIO_OUTPUT_PIN_NUMBER, &config_out);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_gpiote_in_init(GPIOTE_INPUT_PIN_NUMBER, &config_in,NULL);
    APP_ERROR_CHECK(err_code);


    err_code = nrf_drv_ppi_channel_alloc(&ppi_channel);
    APP_ERROR_CHECK(err_code);

    in_evt_addr = nrf_drv_gpiote_in_event_addr_get(GPIOTE_INPUT_PIN_NUMBER);
    gpiote_task_addr = nrf_drv_gpiote_out_task_addr_get(GPIO_OUTPUT_PIN_NUMBER);

    err_code = nrf_drv_ppi_channel_assign(ppi_channel, in_evt_addr, gpiote_task_addr);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_ppi_channel_enable(ppi_channel);
    APP_ERROR_CHECK(err_code);

    nrf_drv_gpiote_out_task_enable(GPIO_OUTPUT_PIN_NUMBER);
    nrf_drv_gpiote_in_event_enable(GPIOTE_INPUT_PIN_NUMBER, true);
}