Why does the nRF5 SDK ship with an outdated nrfx module?

[Andy]

Hi,

I'm currently porting a project to nRF5 SDK17. Some time ago we decided to use the nrfx module as a fork of https://github.com/NordicSemiconductor/nrfx.

So I synced our fork with the latest master in Nordic's own nrfx repository, and our project doesn't compile with it using the latest SDK. Then I realized that SDK 17 is using nrfx v1.8.4, when the latest version available is v2.2.0.

Is there a reason why the nRF5 SDK does not ship with the most up-to-date nrfx? Are there any advantages/disadvantages of using the nrfx module straight from Github?

Thanks.

[Kenneth]

From my understanding there was a change between v1.x and v2.x, and v1.x is compatible with nRF5 SDK, while v2.x is compatible with nRF Connect SDK (based on zephyr RTOS). However both v1.x and v2.x should have been updated in parallel, so both should for most part provide the same functionality.

[Andy]

Hi Kenneth,

So I'm migrating the bootloader from SDK 15 to SDK 17, using the latest nrfx v2.2.0. In version 1.8.4 there use to be functions in the nrf_nvmc module to write bytes/words to flash, but these functions are not available in v2.x anymore.

How can I migrate the code that uses those functions? Specifically, the function that I need is `nrf_nvmc_write_word`.

[Andy]

The changelog indicates that there is a migration guide to move from nrfx v1.x to v2.x but I can't find it anywhere.

[Andy]

Figured it out, but I still couldn't find the migration guide.