GPIOTE + PPI SDK v2.5.2 issue + zephyr

RE: GPIOTE + PPI SDK v2.5.2 issue + zephyr

PW — Fri, 05 Jul 2024 08:24:56 GMT

Thanks.I see, there is a lot of differences between SDK2.6.0 and github zephyrproject-rtos/hal_nordic repo, especcialy in nrfx_gpiote.c. So situation is unstable :)

RE: GPIOTE + PPI SDK v2.5.2 issue + zephyr

LucaMarongiu — Thu, 04 Jul 2024 20:44:52 GMT

Hi, when i faced the problem i also discovered that the solution i adopted was working only for SDK 2.5.2... you must perform a porting for your reference SDK, however i can put here the solution just for reference:

	/////////// GPIOTE configuration ///////////
	// Enable a GPIOTE channel in IN mode. 
	nrfx_gpiote_input_config_t gpiote_cfg;

	gpiote_cfg.pull = NRF_GPIO_PIN_PULLUP; // Enable pullup to stabilize the input signal
	// set trigger configuration

	nrfx_gpiote_trigger_config_t trigger_cfg;

	// Set the GPIOTE channel to be triggered by a rising edge
	trigger_cfg.trigger = NRFX_GPIOTE_TRIGGER_LOTOHI;

	// Allocate a GPIOTE channel
	uint8_t in_channel;
	err = nrfx_gpiote_channel_alloc(&in_channel);
    if(err != NRFX_SUCCESS)
	{
		LOG_ERR("Failed to allocate GPIOTE channel");
		return -1;
	}
	trigger_cfg.p_in_channel = &in_channel;
	err = nrfx_gpiote_input_configure(pin, &gpiote_cfg, &trigger_cfg, NULL);
	if(err != NRFX_SUCCESS)
	{
		LOG_ERR("Failed to configure GPIOTE input");
		return -1;
	}
	// enable the trigger event without using the interrupt mode (PPI has to handle the event)
	nrfx_gpiote_trigger_enable(pin, false);
	////////////////////////////////////////////

	/////////// TIMER configuration ///////////
	// Initialize the timer in counter mode, with 32-bit width and 16MHz frequency

	nrfx_timer_config_t timer_cfg = NRFX_TIMER_DEFAULT_CONFIG(NRF_TIMER_BASE_FREQUENCY_16MHZ);

	timer_cfg.mode = NRF_TIMER_MODE_COUNTER;
	timer_cfg.bit_width = NRF_TIMER_BIT_WIDTH_32;
	err = nrfx_timer_init(&timer_inst, &timer_cfg, NULL);
	if(err != NRFX_SUCCESS)
	{
		LOG_ERR("Failed to initialize timer");
		return -1;
	}
	///////////////////////////////////////////

	/////////// PPI configuration ///////////
	// Set up a PPI channel to connect the GPIOTE event to the timer COUNT task
	uint8_t gppi_ch;
	// Allocate a PPI channel
	err = nrfx_gppi_channel_alloc(&gppi_ch);
	if(err != NRFX_SUCCESS)
	{
		LOG_ERR("Failed to allocate PPI channel");
		return -1;
	}

	// Set up the PPI: connect the GPIOTE event to the timer COUNT task
	nrfx_gppi_channel_endpoints_setup(gppi_ch, nrfx_gpiote_in_event_address_get(pin), nrfx_timer_task_address_get(&timer_inst, NRF_TIMER_TASK_COUNT));

	nrfx_gppi_channels_enable(BIT(gppi_ch));
	///////////////////////////////////////////

	// Enable the timer
	nrfx_timer_enable(&timer_inst);

RE: GPIOTE + PPI SDK v2.5.2 issue + zephyr

PW — Thu, 04 Jul 2024 20:41:05 GMT

Hi. I try to make measurement of low level signal (10us-2ms). I know I should configure both edges on gpioe, but I have problem with timer and ppi. Could you help me with gpioe, timer and ppi config? It will be work on SDK2.6.0

Best regards. PW

RE: GPIOTE + PPI SDK v2.5.2 issue + zephyr

LucaMar — Thu, 07 Mar 2024 14:49:16 GMT

I solved!

I was assigning the wrong channel to the GPIOTE trigger configuration, I was assigning the one of the PPI channel, instead a new one needs to be allocated in this way:

	uint8_t out_channel;
	err = nrfx_gpiote_channel_alloc(&out_channel);
    NRFX_ASSERT(err == NRFX_SUCCESS);
	trigger_cfg.p_in_channel = &out_channel;
	err = nrfx_gpiote_input_configure(pin, &gpiote_cfg, &trigger_cfg, NULL);
	NRFX_ASSERT(err == NRFX_SUCCESS);
	nrfx_gpiote_trigger_enable( pin, false);

RE: GPIOTE + PPI SDK v2.5.2 issue + zephyr

Kenneth — Thu, 07 Mar 2024 14:22:52 GMT

Hello,

Conseptually it seems you are at least on the right track. For debugging maybe check that you get the IN event in the first place by just reading if the event is set in the gpiote peripheral. Also, double check that the pin used is configured as an input. To check if the timer works as intended you can also just manually write to the count task to check if it does count.

I assume you have looked at the nrfx samples:
https://github.com/zephyrproject-rtos/hal_nordic/tree/master/nrfx/samples/src

Kenneth