nRF9160 > Count pulse on GPIO

RE: nRF9160 > Count pulse on GPIO

Oleh — Tue, 29 Oct 2019 09:49:32 GMT

Hi Didrik,

you just rock! thank you for all your support!

Best

Oleh

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Tue, 29 Oct 2019 08:55:24 GMT

After digging some more through the nrfx drivers, I also found the nrfx_dppi_channel_disable (and _enable) functions, which should let you stop and start the specific DPPI channel.

RE: nRF9160 > Count pulse on GPIO

Oleh — Tue, 29 Oct 2019 08:25:32 GMT

Hi and thank you for your input.

I managed to update and make the code working! great! thank you!

Regarding the Suspend/Resume, just for info: I need it in order to save power, as the sensor is external and connected to a stepup convertor, so when not in use -- I would like to power it off. Thus also disable DPPI.

Best regards

Oleh

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Mon, 28 Oct 2019 16:31:16 GMT

Hi, and sorry for the late reply.

For resetting counters, I would use the nrfx_timer_clear function.

For suspending/resuming DPPI, you would have to either stop the events from being generated, not publish the events, or subscribe to them (or all at once).

RE: nRF9160 > Count pulse on GPIO

Oleh — Thu, 24 Oct 2019 08:58:26 GMT

Hello and thank you!

short question: what is the best way to suspend / resume the ppi in this sample?

and how to safely reset counters?

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Thu, 24 Oct 2019 08:34:38 GMT

Hi.

A pull request for a sample demonstrating how to use the nrfx drivers in Zephyr was just opened.

Hopefully, it is able to help you.

https://github.com/zephyrproject-rtos/zephyr/pull/20089/files

Best regards,

Didrik

RE: nRF9160 > Count pulse on GPIO

Oleh — Wed, 23 Oct 2019 13:26:56 GMT

thank you, now I am trying to make it working on the latest ncs git... but getting errors...

is there anything I have to change?

***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****
starting application...
starting init gpiote...
prepare time 1 cfg...
uninit time 1...
init time 1...
prepare time 2 cfg...
uninit time 2...
init time 2...
nrfx_timer_ms_to_ticks...
nrfx_timer_extended_compare...
gpiote_setup...
gpiote_setup...
gpiote_evt_addr: 0x5000d100
NRF_GPIOTE_EVENTS_IN_0: 0x00000100
NRF_GPIOTE1_NS: 0x40031000
gpiote_evt_addr - NRF_GPIOTE0_S: 0x0ffdc100
[00:00:00.069,274] <err> os: ***** BUS FAULT *****
[00:00:00.069,274] <err> os: Precise data bus error
[00:00:00.069,274] <err> os: BFAR Address: 0x40010088
[00:00:00.069,305] <err> os: r0/a1: 0x00000000 r1/a2: 0x00000001 r2/a3: 0x80000000
[00:00:00.069,305] <err> os: r3/a4: 0x40010088 r12/ip: 0x00000030 r14/lr: 0x0000061f
[00:00:00.069,305] <err> os: xpsr: 0x29000000
[00:00:00.069,305] <err> os: Faulting instruction address (r15/pc): 0x00000632
[00:00:00.069,335] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception
[00:00:00.069,335] <err> os: Current thread: 0x20000274 (unknown)
[00:00:00.140,075] <err> os: Halting system

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Tue, 27 Aug 2019 11:36:09 GMT

Hi, and apologies for the late answer.

I believe that most of the code you posted should work, but especially the parts concerning PPI would not work due to differences between PPI and DPPI.

I was able to port an example written by Jared for another case. The sample is made to measure much higher frequencies than what you have, so you might want to edit some of the timer configurations in main().

devzone.nordicsemi.com/.../dppi_5F00_frequency.zip

To make the sample compile, you must also add

#define GPIOTE_IRQn GPIOTE0_IRQn

in ncs/zephyr/ext/hal/nordic/nrfx_config_nrf9160.h, on line 200.

Also, you must configure the DPPI peripheral as non-secure as done in a previous comment.

A pre-compiled hex file is included for your convenience.

Best regards,

Didrik

RE: nRF9160 > Count pulse on GPIO

Oleh — Wed, 21 Aug 2019 07:17:55 GMT

am I on the right way?

static void timer_init()
{
 NRF_TIMER1_NS->TASKS_STOP = 1;
 NRF_TIMER1_NS->MODE = TIMER_MODE_MODE_Timer;
 NRF_TIMER1_NS->PRESCALER = 8; // Fhck / 2^8 
 NRF_TIMER1_NS->CC[0] = 62500; // 62500 - 1s
 
 NRF_TIMER1_NS->BITMODE = (TIMER_BITMODE_BITMODE_16Bit << TIMER_BITMODE_BITMODE_Pos); 
 
 NRF_TIMER1_NS->TASKS_CLEAR = 1;
 NRF_TIMER1_NS->INTENSET = (TIMER_INTENSET_COMPARE0_Enabled << TIMER_INTENSET_COMPARE0_Pos);
 
 NRF_TIMER1_NS->EVENTS_COMPARE[0] = 0;
}

static void counter_init()
{
 NRF_TIMER2_NS->TASKS_STOP = 1; 
 NRF_TIMER2_NS->MODE = TIMER_MODE_MODE_Counter;
 NRF_TIMER2_NS->BITMODE = (TIMER_BITMODE_BITMODE_24Bit << TIMER_BITMODE_BITMODE_Pos);
 NRF_TIMER2_NS->TASKS_CLEAR = 1;
 NRF_TIMER2_NS->EVENTS_COMPARE[0] = 0;
}

#define SENSE_PIN 13
static void gpiote_init(uint32_t pin)
{
 NRF_GPIOTE1_NS->CONFIG[0]  =  0x01 << 0;         // MODE: Event
 NRF_GPIOTE1_NS->CONFIG[0]  |=  SENSE_PIN << 8;       // Pin number
 NRF_GPIOTE1_NS->CONFIG[0]  |=  NRF_GPIOTE_POLARITY_LOTOHI << 16;  // Event rising edge  
}

static void ppi_timer_stop_counter_init()
{
 //NRF_DPPIC_NS->CHEN |= 1 << 0;
 //*(&(NRF_DPPIC_NS->CH0_EEP)) = (uint32_t)&NRF_TIMER1_NS->EVENTS_COMPARE[0];
 //*(&(NRF_DPPIC_NS->CH0_TEP)) = (uint32_t)&NRF_TIMER2_NS->TASKS_STOP;
 //NRF_DPPIC_NS->CHENSET |= 1 << 0;
 
 #define EVT_IX_TIMER1__COMPARE 1
 #define TSK_IX_TIMER2__STOP_COUNTER 1
    // Configure GPIOTE Index 0 to be an Event -> 
    nrf_gpiote_event_configure(EVT_IX_TIMER1__COMPARE, nrf_timer_event_address_get(NRF_TIMER1_NS, NRF_TIMER_EVENT_COMPARE_1) ...);
    // Configure GPIOTE Index 1 to be a Task -> 
    nrf_gpiote_task_configure(TSK_IX_TIMER2__STOP_COUNTER, nrf_timer_event_address_get(NRF_TIMER2_NS, NRF_TIMER_TASK_COUNT) ...);
    // Index 0 will Publish on DPPI Channel 0 
    nrf_gpiote_publish_set(NRF_GPIOTE_EVENTS_IN_0, DPPI_CHANNEL);
    // Index 1 will Subscribe on DPPI Channel 0 
    nrf_gpiote_subscribe_set(NRF_GPIOTE_TASKS_OUT_1, DPPI_CHANNEL);
    // Enable Publish and Subscribe 
    nrf_gpiote_event_enable(EVT_IX_TIMER1__COMPARE);
    nrf_gpiote_task_enable(TSK_IX_TIMER2__STOP_COUNTER);
    // Enable DPPI Channel 
    nrf_dppi_channels_enable(NRF_DPPIC, DPPI_BIT_SET(DPPI_CHANNEL));
}

static void ppi_gpiote_counter_init()
{
 NRF_DPPIC_NS->CHEN |= 1 << 1;
 *(&(NRF_DPPIC_NS->CH1_EEP)) = (uint32_t)&NRF_GPIOTE1_NS->EVENTS_IN[0];
 *(&(NRF_DPPIC_NS->CH1_TEP)) = (uint32_t)&NRF_TIMER2_NS->TASKS_COUNT;
 NRF_DPPIC_NS->CHENSET |= 1 << 1;
}

RE: nRF9160 > Count pulse on GPIO

Oleh — Tue, 20 Aug 2019 21:12:51 GMT

Hi Didrik, thanks! that was to make the ppi_trace to work.

could you please help on wiring Counter and Timer to get it with DPPI as here: https://devzone.nordicsemi.com/f/nordic-q-a/9036/measuring-input-gpio-pin-frequency-with-soft-device-running ?

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Tue, 20 Aug 2019 08:58:54 GMT

Almost.

In addition to

PERPIH("NRF_DPPI", NRF_DPPIC_NS, CONFIG_SPM_NRF_DPPIC_NS),

in spm.c:304 and

if (IS_ENABLED(CONFIG_SPM_NRF_GPIOTE1_NS)) {
    NRF_SPU->DPPI[0].PERM = 0;
}

in spm.c:326

I also had to add

PERIPH("NRF_RTC0", NRF_RTC0, CONFIG_SPM_NRF_RTC0_NS),

in spm.c:305,

config SPM_NRF_DPPIC_NS
	bool "DPPI is Non-Secure"
	default y

config SPM_NRF_RTC0_NS
	bool "RTC0 is Non-Secure"
	default y

in ncs/nrf/subsys/spm/Kconfig:180, and

CONFIG_PPI_TRACE_PIN_RTC_COMPARE_EVT=10
CONFIG_PPI_TRACE_PIN_RTC_TICK_EVT=11
CONFIG_PPI_TRACE_PIN_LFCLOCK_STARTED_EVT=12

in prj.conf

RE: nRF9160 > Count pulse on GPIO

Oleh — Mon, 19 Aug 2019 15:00:59 GMT

aha! that was the missing part, thank you!

I will try for the Secure board.

In order to use DPPI on the NonSecure, would this be sufficient:

PERIPH("NRF_DPPI", NRF_DPPIC_NS, CONFIG_SPM_NRF_DPPIC_NS), // adding to spm.c in the periph_cfg periph[]

And also:

if (IS_ENABLED(CONFIG_SPM_NRF_GPIOTE1_NS)) {
/* Configure DPPI to be Non-Secure */
NRF_SPU->DPPI[0].PERM = 0;
}

thank you!

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Mon, 19 Aug 2019 14:54:41 GMT

The ppi_trace sample worked for me.

I did not get any build errors.

However, I did have to change the pins used to 10, 11, and 12. You can do this in the Kconfig file in the sample, or by adding the relevant configurations in the prj.conf file.

Also, the sample should be built as a secure application (use target nrf9160_pca10090, no ns).

RE: nRF9160 > Count pulse on GPIO

Oleh — Sun, 18 Aug 2019 11:31:17 GMT

thanks for the hint! I'm trying it out...

first blocker was: https://devzone.nordicsemi.com/f/nordic-q-a/49657/how-to-link-nrfx-gpiote-and-ppi-in-zephyr/198090#198090 when adding the config -- it picked up.

second blocker is "GPIOTE_IRQn undeclared" for nRF9160 (there are two: GPIOTE0_IRQn/GPIOTE0_IRQn defined in \zephyr\ext\hal\nordic\nrfx\mdk\nrf9160.h)

am I missing something? Or was the ppi_trace never configured+tested on nRF9160?

Thanks!

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Fri, 09 Aug 2019 11:16:45 GMT

Yes, you can use GPIOTE and DPPI on the nRF91.

It looks like Zephyr's GPIO driver uses GPIOTE internally.

The PPI trace sample works with both nRF91 and nRF52 and might be a good starting point on how to use DPPI.

RE: nRF9160 > Count pulse on GPIO

Oleh — Fri, 09 Aug 2019 10:14:20 GMT

Hi, thank you!

Just a short confirmation question: can I use Gpiote/PPI in Zephyr with nrf91?

Best

Oleh

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Thu, 08 Aug 2019 08:45:58 GMT

Hi.

Here is the code I used to count pulses. It does not calculate the frequency, but that should be easy to do if you see how many pulses you get per unit of time.

devzone.nordicsemi.com/.../reader.zip

Best regards,

Didrik

RE: nRF9160 > Count pulse on GPIO

Oleh — Thu, 08 Aug 2019 06:51:47 GMT

Hi Didrik,

thank you for the suggestion, It is clear with the pwm part, got it working.

what i am not able to catch is the sensing that frequency on the input part. Tried the gpio to config in input, then reading buffer, seems ok to get bits 0s/1s but somehow to get to the frequency not... i’m stuck.

May I ask you for a snippet?

thank you!

best

Oleh

RE: nRF9160 > Count pulse on GPIO

Oleh — Fri, 19 Jul 2019 18:39:07 GMT

Hi Didrik,

thank you! will try all of it 🙂

Best regards

Oleh

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Thu, 18 Jul 2019 11:40:36 GMT

Hi.

Take a look at the PWM driver documentation.

Best regards,

Didrik

RE: nRF9160 > Count pulse on GPIO

Oleh — Thu, 18 Jul 2019 09:38:42 GMT

Hi Didrik,

thank you, I'm new to Zephyr so trying to map my nrf knowledge to zephyr 🙂

To complement and test the counter on gpio, I thought to put the second DevKit board into generation mode. Could you please point on the right track with how can the generation on-off be done in background on Zephyr?

thanks & best

Oleh

RE: nRF9160 > Count pulse on GPIO

Didrik Rokhaug — Thu, 18 Jul 2019 08:39:47 GMT

Hi.

You can use Zephyr's GPIO driver to configure interrupts.

Have a look at the documentation here.

Best regards,

Didrik