nrf52 ADC code based on nrfx 1.7.0 won't work on nrfx 2.1.0.

RE: nrf52 ADC code based on nrfx 1.7.0 won't work on nrfx 2.1.0.

Jørgen Holmefjord — Wed, 03 Jun 2020 16:19:29 GMT

Hopefully, there will be some documentation/examples with the new driver in the next SDK release. For details on when that will be available, you need to contact your regional sales manager.

[quote user="shanyechungu"]Also, regarding Mynewt, do you suggest them to backport to 1.8.x as well?[/quote]

Not necessarily, but I would recommend updating the sample/documentation to work with the new API. We are using nrfx 2.x.x in nRF Connect SDK, but it looks like the SAADC implementation in Zephyr is using HAL functions and not the new nrfx_saadc driver, so this does not provide any useful information about how to use the new API.

RE: nrf52 ADC code based on nrfx 1.7.0 won't work on nrfx 2.1.0.

shanyechungu — Wed, 03 Jun 2020 15:31:56 GMT

Hi Jorgen,

Thank you for your response, although, this is a sort of disappointing.

May I know if there is a timeline Re: when the support document will be available?

Also, regarding Mynewt, do you suggest them to backport to 1.8.x as well?

Thanks,

RE: nrf52 ADC code based on nrfx 1.7.0 won't work on nrfx 2.1.0.

Jørgen Holmefjord — Wed, 03 Jun 2020 09:21:40 GMT

Hi,

As you figured, the nrfx 2.x API is not supported in the nRF5 SDK exactly because of the large changes in the SPI of the new nrfx_saadc driver. The driver have been completely rewritten to fix some issues seen with the old driver. The new driver will be backported to nrfx v1.8.x in the next release of nRF5 SDK, but the legacy driver will still be available. The example code needs to be completely rewritten to support the new driver. Unfortunately, for now, we do not have any examples available for the new driver. I would recommend you to stick with the driver from nrfx v1.8.x for now.

Best regards,
Jørgen