How to link nrfx GPIOTE and PPI in Zephyr?

RE: How to link nrfx GPIOTE and PPI in Zephyr?

PopradiArpad — Thu, 18 Jul 2019 15:49:18 GMT

Hi Didrik,

thank you!

Simply putting a Kconfig file with this content:

config ACTIVATE_NRFX_PPI_AND_GPIOTE
bool "Turn on the invisible NRFX_PPI and NRFX_GPIOTE options"
select NRFX_PPI if HAS_HW_NRF_PPI
select NRFX_GPIOTE if HAS_HW_NRF_GPIOTE
help
Turn on the invisible NRFX_PPI and NRFX_GPIOTE options.

source "Kconfig.zephyr"

into the project folder and using it in the prj.conf:

CONFIG_ACTIVATE_NRFX_PPI_AND_GPIOTE=y

does it.

Best regards,

Árpád

RE: How to link nrfx GPIOTE and PPI in Zephyr?

Didrik Rokhaug — Thu, 18 Jul 2019 13:37:40 GMT

Hi.

You can add your own Kconfig file in your application, similar to the PPI trace sample.

Best regards,

Didrik

RE: How to link nrfx GPIOTE and PPI in Zephyr?

PopradiArpad — Fri, 12 Jul 2019 09:20:59 GMT

These are the invisible Kconfig options which can not be set directly from the prj.conf or menuconfig.

The project https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/debug/ppi_trace

shows another way:

1. define a visible Kconfig option which selects the options above (the second select is different then in https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/subsys/debug/ppi_trace/Kconfig):

menuconfig PPI_TRACE
	bool "Enable PPI trace"
	select NRFX_PPI if HAS_HW_NRF_PPI
	select NRFX_GPIOTE if HAS_HW_NRF_GPIOTE
	help
	Enable PPI trace module which enables forwarding hardware events to
	GPIOs.

2. use this new option in the prj.conf

CONFIG_PPI_TRACE=y

This works but currently I hacks the Zephyr main Kconfig to define this visible option.

What is the right solution without hacking Zephyr?

RE: How to link nrfx GPIOTE and PPI in Zephyr?

Martin Lesund — Fri, 12 Jul 2019 08:49:44 GMT

I may have been a bit quick with my answer.

Please try to enable with:

CONFIG_NRFX_GPIOTE=y

CONFIG_NRFX_PPI=y

RE: How to link nrfx GPIOTE and PPI in Zephyr?

PopradiArpad — Fri, 12 Jul 2019 08:21:08 GMT

Hi Martin,

as I see these examples creates a new Kconfig option CONFIG_PPI_TRACE which when selected selects the not directly selectable CONFIG_NRFX_PPI. What I don't see, how to integrate this Kconfig fragment into the Kconfig tree to parse without hacking Zephyr?

Best regards,

Árpád

RE: How to link nrfx GPIOTE and PPI in Zephyr?

PopradiArpad — Fri, 12 Jul 2019 07:43:00 GMT

It seems to me that the problem is the missing PPI setup.

How can I activate the PPI by Kconfig?

RE: How to link nrfx GPIOTE and PPI in Zephyr?

PopradiArpad — Fri, 12 Jul 2019 07:33:16 GMT

Hi Martin,

thanks for the quick answer.

I have updated my prj.conf with the 3 config options above but got the same problem.

You mean

#include <nrfx_gpiote.h>

and not

#include <nrf_gpiote.h>

I think.

I study the code samples you lists yet.

Best regards,

Árpád

RE: How to link nrfx GPIOTE and PPI in Zephyr?

Martin Lesund — Fri, 12 Jul 2019 07:17:44 GMT

Hi Árpád,

PPI is used in the PPI trace sample:

https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/debug/ppi_trace

And the subsys (sub system):

https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/subsys/debug/ppi_trace/ppi_trace.c

The sample can be used both for 52 and 91 so that’s why the sample is called “PPI”. (nrf91 uses DPPI)

In the code you have for example:

#ifdef DPPI_PRESENT which will in turn use the nrfx_dppi_channel_alloc() function.

(while if not DPPI_PRESENT then it’s the “standard” nrfx_ppi_channel_alloc())

So in your case, you should use this sample as a reference on how to use PPI for nrf52.

Remember to add:

#include <nrfx_ppi.h>
#include <nrf_gpiote.h>

Have you made sure to enable these configurations in either "ninja menuconfig" or adding it in prj.conf?

CONFIG_GPIO=y

CONFIG_GPIO_NRFX=y

CONFIG_GPIO_NRF_P0=y

best regards,
martin L.