NRF52 FW backward Compatibility

RE: NRF52 FW backward Compatibility

haakonsh — Wed, 22 May 2019 07:21:27 GMT

No SoftDevice is compatible with both series.
If you mean outside of the SDK, then there are one dependency I can think of, the optional µECC library. We have our own crypto library so you do not have to use the µECC library.

RE: NRF52 FW backward Compatibility

Prajakta — Wed, 22 May 2019 05:34:18 GMT

Few questions -
1. Which version of the SoftDevice is compatible with both NRF51 and NRF52?

2. Are there any dependencies on the other libraries, framework used in the FW build?

RE: NRF52 FW backward Compatibility

Prajakta — Wed, 22 May 2019 05:28:34 GMT

After changes in libraries. Code would work for both nrf51 and nrf52 chip?

RE: NRF52 FW backward Compatibility

Ruth Fuchss — Tue, 21 May 2019 09:43:29 GMT

There's a high-level migration guide here: https://infocenter.nordicsemi.com/topic/migration_nrf52/MIG/nrf52_migration/preface.html
But it hasn't been updated for a while, so it's not targeting the current SDK.

RE: NRF52 FW backward Compatibility

haakonsh — Tue, 21 May 2019 09:34:24 GMT

The difference in APIs are fairly big. I strongly urge you to start over with SDK 15.3. You can reuse a lot of your code from custom services and much of your program flow, but almost all calls to libraries are changed. Previous experience with BLE and the nRF51 SDK will help you a lot of course.