RE: Mismatch between nrfx 2.4.0 and SDK 17.0.2???

essele — Thu, 14 Jan 2021 10:30:17 GMT

Hi Jørgen,

Thanks for the comprehensive answer ... it's a little disappointing and feels like it will create more work in the future, but understood.

I got the ADC working pretty quickly actually ... it just feels wrong that it's not using the newest API's.

Thanks,

Lee.

RE: Mismatch between nrfx 2.4.0 and SDK 17.0.2???

Jørgen Holmefjord — Wed, 13 Jan 2021 13:25:08 GMT

Hi,

nrfx v2.x.x is not supported by nRF5 SDK, and will most likely not be supported in the future either. nRF5 SDK supports the nrfx 1.8.x branch, and this is the recommended use for nRF5 SDK. For other SDKs and RTOSes, like nRF Connect SDK, nrfx v2.x.x is supported.

Regarding the nrfx_saadc driver, there is two APIs available (#1 - #2). The driver was totally rewritten to resolve a few issues. Initially, the new API was only supported in nRFx v2.x.x, but this API was backported to nrfx v1.8.4 in used in SDK 17.0.0. Both API versions are available in nrfx v1.8.4 and later, you can switch between the APIs in compile-time with the preprocessor symbol NRFX_SAADC_API_V2. Some examples of the new API can be found in the nrfx GitHub wiki, but I also provided some examples for use with nRF5 SDK v 17.x.0 in this repository.

[quote user=""]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??[/quote]

I agree that legacy is not the best name for the "legacy driver APIs", integration may have been better. There is no real advantage in switching to the nrfx APIs when using nRF5 SDK, as the legacy layer will use nrfx driver in the bottom layer anyway. Most of the libraries in the SDK is also not migrated to use the nrfx APIs directly.

Best regards,
Jørgen