52832 PPI and GPIOTE, TIMER

RE: 52832 PPI and GPIOTE, TIMER

Jared — Wed, 23 Nov 2022 11:35:34 GMT

Hi,

So now it works?

regards

Jared

RE: 52832 PPI and GPIOTE, TIMER

K-night — Wed, 23 Nov 2022 05:49:41 GMT

yes, I added "nrf_drv_gpiote_out_config_t config = GPIOTE_CONFIG_OUT_TASK_TOGGLE(false);" before my GPIOTE init, now it is ok.

thanks

RE: 52832 PPI and GPIOTE, TIMER

K-night — Tue, 22 Nov 2022 01:30:58 GMT

not toggle, I hope when compare pin output low, and GPIOTE output low,

compare pin output high, and GPIOTE output high,

but I check compare high and low register are correct, GPIOTE pin doesn't output, does my GPIOTE output pin register set wrong?

RE: 52832 PPI and GPIOTE, TIMER

Jared — Mon, 21 Nov 2022 14:51:38 GMT

Hi there,

On exactly what condition do you want your pin to toggle? I see that you set compare_evt_addr_down and compare_evt_addr_up but don't' actually use them in the code? Right now you set the pin to toggle when timer 0 and timer 1 generate a COMPARE event based on CC[0]. You also need to initialize m_gpiote correctly before passing it to nrf_drv_gpiote_out_init().

    nrf_drv_gpiote_out_config_t config = GPIOTE_CONFIG_OUT_TASK_TOGGLE(false);

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

regards

Jared