Migration from NCS 2.9.0 to NCS 3.2.1 is hard, not well documented and will break all nrfx code.

RE: Migration from NCS 2.9.0 to NCS 3.2.1 is hard, not well documented and will break all nrfx code.

Ingfu — Fri, 13 Feb 2026 08:40:57 GMT

Especially with the new EU regulations (CRA) and the neccessary vulnerability management, I'd like to keep my project at least during development up-to-date and target the latest SDK version to be sure, that I don't ship a device with possible vulnerabilities. We will also need to support updates, so it will probably necceessary to update the SDK later as well. I'd suggest to be more careful with major changes.

RE: Migration from NCS 2.9.0 to NCS 3.2.1 is hard, not well documented and will break all nrfx code.

BrianW — Mon, 09 Feb 2026 15:10:07 GMT

[quote userid="2111" url="~/f/nordic-q-a/126896/migration-from-ncs-2-9-0-to-ncs-3-2-1-is-hard-not-well-documented-and-will-break-all-nrfx-code/560692"]Hope this helps,[/quote]

pretty much not at all.

[quote userid="2111" url="~/f/nordic-q-a/126896/migration-from-ncs-2-9-0-to-ncs-3-2-1-is-hard-not-well-documented-and-will-break-all-nrfx-code/560692"]even when each individual change may make sense on its own.[/quote]

If you assumed that noone would ever migrate from an older version of NCS, then yes, maybe refactoring your code to be 'nicer' makes sense.

But given the frequent response on this fourm is "try updating to latest version", its not developer friendly to make breaking changes even when there is no actual need to do so. This just means your products get a bad reputation.

I suggest you feed this back to the nrfx lib development team, and get them to work on a migration update that makes the process possible.... and work out a way so make wifi support possible without using up all the flash!

RE: Migration from NCS 2.9.0 to NCS 3.2.1 is hard, not well documented and will break all nrfx code.

Kenneth — Mon, 09 Feb 2026 14:52:11 GMT

Hello,

Your feedback is noted and forwarded. I know this is something that’s being looked into, as the frequent changes can be frustrating, even when each individual change may make sense on its own.

I suggest you break down the issues you encounter and make individual case for each of them.

Hope this helps,
Kenneth

RE: Migration from NCS 2.9.0 to NCS 3.2.1 is hard, not well documented and will break all nrfx code.

BrianW — Mon, 09 Feb 2026 13:54:46 GMT

Some clues for those also trying to migrate:

NCS 3.1.1 : does NOT have nrfx4 nor zephyr 4.2, but does have changes to wifi and mqtt code.

NFC : NCS3.1.1 fails to compile my nfc code, can't find <nfc_t4t_lib.h>

- because CONFIG_NFC_T4T_NRFXLIB gets set to 'n'

- due to not having CONFIG_HAS_HW_NRF_NFCT

which is because this is now (since 3.1?) dependant on having the nfc explicitly set to okay in your DTS

&nfct {

status = "okay";

};

Once this is done its ok and the link works too.

(strangely ncs 3.2.1 accepted to compile my source, so with the include, but failed at the link...)