gpiote get task address

RE: gpiote get task address

Morgan Jones — Fri, 21 Oct 2016 17:17:30 GMT

I ran across this same problem and also noticed that the nrf_drv_gpio_ driver doesn't address those set and clr tasks. I just managed to successfully use this as a way to get those addresses:

uint32 pin_out_task_addr = nrf_drv_gpiote_out_task_addr_get(PIN_OUT);    
uint32 pin_set_task_addr = pin_out_task_addr + 0x30;
uint32 pin_clear_task_addr = pin_out_task_addr + 0x60;

Ie, just adding the register offsets from here:

infocenter.nordicsemi.com/index.jsp

It's not a perfect method, but is working great for me.

RE: gpiote get task address

Jørgen Holmefjord — Thu, 20 Oct 2016 10:35:02 GMT

Can you post an example of how you do it with entering the address manually? And explain in more detail what you try to achieve?

RE: gpiote get task address

bds — Wed, 19 Oct 2016 15:26:42 GMT

Hi,

as I understand these functions, nrf_drv_gpiote_out_task_addr_get() gives the address of the OUT task. And the OUT task can be configured to toggle, set or clear a pin. But there are also dedicated SET and CLR tasks with their own address for PPI usage. I need these addresses in PPI to configure different events triggering set and clear tasks through the same GPIOTE channel. This seems to work if I enter the addresses manually, but I could'nt find any function to get these addresses in the SDK.

RE: gpiote get task address

Jørgen Holmefjord — Wed, 19 Oct 2016 15:08:15 GMT

Hi,

The function nrf_drv_gpiote_out_task_addr_get() return the address of the task, which you can use to configure PPI or control the task manually. You can take a look at the function led_blinking_setup() in the GPIOTE example. Here GPIOTE is used to connect a timer to a GPIO port, using PPI, to toggle a LED. Toggle is selected by configuring the GPIOTE pin using GPIOTE_CONFIG_OUT_TASK_TOGGLE. It would also have been possible to set or clear the GPIO by configuring the pin using GPIOTE_CONFIG_OUT_TASK_LOW or GPIOTE_CONFIG_OUT_TASK_HIGH.

Best regards,

Jørgen