RE: Issue with 2 hw timer interrupt collision

sxd248 — Tue, 17 Mar 2020 15:27:50 GMT

First of all thank you so much for helping me with this issue! You were right in that the issue was with the handling of the gpio registers. I changed it now to follow what the HAL does, which is just set the OUTSET and OUTCLEAR register equal to 1 << pinnum. Thanks again! PS. Ur libraries are good, I just like to know how it all works 🙂.

RE: Issue with 2 hw timer interrupt collision

Edvin — Tue, 17 Mar 2020 10:19:35 GMT

Hello,

The first that I noticed was the compiler warning that said that you didn't have a type for y on line 61 in gpio.c. Please set it to e.g. uint8_t or uint32_t.

It is actually not an interrupt issue. I ported your code to an example that had logging enabled, and the event handlers were called properly. The issue was in your function:

// Set the output pin low
void gpio_pin_clear(NRF_GPIO_Type *port, uint32_t pin_num)
{
  port-> OUTCLR |= (1 << pin_num);
}

There is a space there between "port->" and "OUTCLR", but I don't think it caused any issues. Just wanted to let you know.

The issue is the "|=".

I played around with the timer values, and noticed that whenever one pin is cleared (LED is turned on), both of them were turned on. The reason for this is that it takes some time to clear the OUTCLR register.

Try to set it to:

port->OUTCLR &= (1 << pin_num);

So, we see that some people insist on using the registers directly, but we do have libraries for these kinds of tasks, that can save you a lot of time if you use them. I suggest that you consider it for the future 🙂

Best regards,

Edvin