Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

nRF NCS 1.9.x GPIOTE bug in gpio_nrfx.c

Hi,
Found a bug (the hard way) in NCS 1.9 that is not reported in the known issues page.
in this static func gpio_nrfx_pin_configure(), pin is passed into nrfx_gpiote_channel_get() whereas it should be abs_pin that get passed in.
    err = nrfx_gpiote_channel_get(pin, &ch);
    free_ch = (err == NRFX_SUCCESS);
It could lead to catastrophic behavior, unregistering/freeing some other pin's GPIOTE channel that has the same PIN but not the same port as it doesn't consider the port.
e.g. if one tries to pin configure P1.14 after P0.14 was assigned a GPIOTE channel, it would cause the channel associated with P0.14 to be freed.
This is fixed in the latest zephyr version, and I suppose some newer NCS version.
 
My main question is: How do I find out all the known issues with a certain nRF NCS version? The known issues of NCS itself doesn't seem to include those of zephyr AND zephyr doesn't seem to have a known issues page!
It seems a very basic requirement for an RTOS that's being used my manufacturers shipping millions of products.
These are the 3 places I looked and no hits:
Searching on Zephyr github for any open issues
Also the nRF fork of Zephyr doens't even allow seeing "issues" which is concerning.
2nd question: Does nordic put any effort into backporting such critical bug into an older NCS?
Is there a LTS version of nRF NCS? or should one go by "latest is greatest" model? Though I'm sure newer versions have more features and potentially new bugs.
Thank you for your help,
FJ
Related