GPIO per-pin DETECT signal available?

RE: GPIO per-pin DETECT signal available?

RK — Fri, 26 Oct 2018 10:35:54 GMT

Each pin does have a separate DETECT signal and you can configure them on and off and positive or negative detects, however the only signal which is output from the GPIO module for you to use is the ORed DETECT. So I supposed you could complain about the words 'by default' but really .. that's rather splitting hairs.

This is again why I like the nRF52 which at least lets you have access to what was DETECTed, not I think that I've ever used that feature.

RE: GPIO per-pin DETECT signal available?

pgruebele — Fri, 26 Oct 2018 08:16:41 GMT

Thanks RK. I am familiar with the items you mention.

Just to be clear:

So the NRF51 does not support separate DETECT signals as stated in the manual? All DETECT signals are OR'ed together and presented in NRF_GPIOTE->EVENTS_PORT as a single bit?

Cheers

Philip

RE: GPIO per-pin DETECT signal available?

RK — Thu, 25 Oct 2018 21:58:52 GMT

well the IN register reads the current state of the pins, is that what you want? Or do you want an event generated on a single pin DETECT? If you want the latter you can have up to 4 pins selected in the GPIOTE module (see section 15) and generate events and interrupts on edge changes. Note that's a higher power mode, details about that power consumption are in the product sheet for the actual chip, not the reference manual which is generic to the series.

If you use the much newer nrf52832, and this is from memory, it has a LATCH register which does exactly that and latches any pin detects so you can find out what *was* detected and not just read IN which tells you what *is* the current state.

Is there a reason you're sticking to the, now, much older chip? The nRF52 has loads of little improvements like this.