Question regarding migrating from sdk14.2 to sdk15.2

[Jesper de]

hello, 

When looking at the 3 different migrations scenarios at 

https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/nrfx_migration_user_guide#getting_started_replace_nrf_drv_options_migrate

we can see that migration is not possible for 3 drivers - for us, the nrf_drv_clock is the one we are using. 

Will it be possible to use the nrfx version of the rest of the drivers (nrf_drv_timer, saadc, wdt) and run with the legacy version of the nrf_drv_clock? 

best regards

Jesper de Fries

[Jørgen Holmefjord]

Hi,

Yes, it is perfectly fine to use the nrfx drivers for the other peripherals. Legacy drivers also use nrfx drivers in the lower layer, there is just a redefinition layer to map the legacy API to the nrfx API.

Best regards,
Jørgen

[Jørgen Holmefjord]

1.  Yes, the nrf_drv_common.c is not needed in SDK 15.2.0, and should be removed.
2. NRF_FSTORAGE_PARAM_CHECK_DISABLED is a sdk_config.h config. If it's not in your sdk_config.h file, you need to add it. See the configs in examples\peripheral\flash_fstorage\pca10040\s132\config\sdk_config.h

[Jesper de]

Thanks for all the answers. There was other issues with undeclared macros which was fixed using the examples as reference.

But now we have a problem with the linker it seems - please see attached picture. 

Do you have any advice on how to proceed?

best regards

Jesper de Fries

[Jørgen Holmefjord]

You are either missing some source files, or the modules are not enabled in sdk_config.h:

• modules\nrfx\mdk\ses_startup_nrf_common.s
• components\libraries\atomic\nrf_atomic.c
• components\libraries\atomic_flags\nrf_atflags.c

There could be more missing files in your project (it say 92 errors, but I think you cut of the image). You should search the files in components folder for the function name that is undefined, and include that source file.