Adding newer SDK features to existing application in SDK v10

[Hieu]

I am working on adding DFU, persistent storage and pair/bond feature to an existing nRF51 application, developed with SDK v10.0.0 running on SoftDevice S110 v8.0.0.

I looked over the SDK documentation a little and found out that:

• S130 v2.0.0 replaced S110 v8.0.0 from SDK v11.0.0
• Flash Storage module is still in experimental in SDK v14.1.0
• Peer Manager is out of experimental from SDK v11.0.0
• Secure DFU is introduced in SDK v12.1.0
• nRF51 is not supported from SDK v13.0.0 on

I am unsure whether I should bring Peer Manager and Flash Storage module from a higher SDK into my project, or use the existing production ready Device Manager and Persistent Storage module.

I also considered migrating to SDK v12.3.0 and S130 v2.1.0. But I am also unsure about the ease of migration and what to do about Flash Storage module and lack of the non-experimental Persistent Storage module

Could someone advise me on what course of action would be the best, considering product's reliability and development time?

[bjorn-spockeli]

Hi Vo,

I recommend migrating to SDK v12.3.0 and S130 v2.1.0 rather than backporting features from the newer SDK versions into SDK v10.0.0

As for the Peer Manager and the Flash Data Storage(FDS) Module, they both offer significant improvements compared to their predecessors (i.e. Device Manager and Persistant Storage). FDS is one of the dependencies of the Peer Manager.

[Hieu]

Hi Bjørn,

Could you please give me some overview about how much work should be done for the migration? We are currently under quite a harsh time constraint.

For your reference, our application only use NUS, DIS and BAS services, and PWM library together with some peripherals operations.