Enabling Backends, interrupts

[AlonBarak]

Hi, 

I am updating SDK version from 15.0 to 17. We are using nrf52840.

I would like to know if these are necessary to add, as they were added in some examples, and if so, what is the reason.

To be clear, we have a stable product that works with SDK 15 and we want to make sure we do this transition correctly.

I would appreciate your response to every one of the defines below:

NRF_CRYPTO_BACKEND_CC310_ECC_CURVE25519_ENABLED 1 

NRF_CRYPTO_BACKEND_CC310_ECC_ED25519_ENABLED 1 

NRF_CRYPTO_BACKEND_CC310_INTERRUPTS_ENABLED 1 

NRF_CRYPTO_BACKEND_OPTIGA_ENABLED 0 

NRF_CRYPTO_BACKEND_OPTIGA_RNG_ENABLED 0 

NRF_CRYPTO_BACKEND_OPTIGA_ECC_SECP256R1_ENABLED 1 

NRF_CRYPTO_CURVE25519_BIG_ENDIAN_ENABLED 0 

CLOCK_CONFIG_LF_CAL_ENABLED 0 

NRFX_WDT_CONFIG_NO_IRQ 0 

FDS_VIRTUAL_PAGES_RESERVED 0 

NRF_BLE_GQ_BLE_OBSERVER_PRIO 1 

NRF_BLE_SCAN_OBSERVER_PRIO 1 

Thanks,

Alon Barak

Qcore Medical

[tesc]

Hi,

Each new major version of the nRF5 SDK has a migration guide covering backwards breaking changes that need to be addressed, when migrating to that major version from the previous one. See nRF5 SDK v16.0.0 Migration Guide and nRF5 SDK v17.0.0 Migration Guide.

Regarding the defines that you list, whether they are needed or not depend on what modules you are using for your project. Some are added functionality and some are changes from previous versions of the modules. Please reference the migration guides, and the nRF5 SDK v17 documentation for the libraries that you use.

Regards,
Terje