I am now pulling my hair out with these drivers ... I'm trying to do what I think is the right thing and use the new nrfx drivers, but it's really not easy.
So this started by me trying to use the SAADC nrfx driver ... I've added the .c file from the nrfx drivers directory, but the init() call didn't match the one in the documentation. After a fair amount of faffing around I discovered that the version of nrfx included in the 17.0.2 SDK download isn't current (at all) ... in fact, according to the change log it's 1.8.6 from 2020-08-31.
So I moved that version out of the way and grabbed 2.4.0 from GitHub. A quick skim of the files and they clearly match the documentation, which is a start.
However ... the changelog show a completely different set of updates and dates, and there's no reference to 1.8.6 anywhere. Is this a different fork?
My app now won't build because the init() function of nrfx_gpiote is different than app_button.c expects for example .... plus quite a few other areas where you now need to provide IRQ levels or register details.
I notice from the "migration guide for nrfx drivers" that there are some library dependencies that "need to be resolved."
So am I right in thinking that in order to use the drivers that are not legacy I need to go and fix a load of library files that are part of the most recently provided SDK? Surely not -- that means that I'll have to do it for each future SDK version??
Lee.
