Migrate softdevice from s132 to s332

[mikefraguglia]

We have a well-vetted software environment what uses SDK 15.3.0 and softdevice s132. We are considering adding ANT+ to our environment, which as I understand requires that we migrate to s332 so that we have ANT while maintaining BLE central and peripheral.

What are the implications of such a migration? 

[Hieu]

Hi mikefraguglia,

In this scenario, you most likely need to do two DFU procedures. 

The first one update the SoftDevice. If your bootloader depends on the SoftDevice, this update also need to include a new bootloader.

After that update, the application is invalidated. The bootloader will enter DFU mode waiting for the application update, which will be the second update.

For more information, plg over all the subpages of the parent topic, Bootloader and DFU modules.

Hieu

[mikefraguglia]

Thank you for your response, it is good information! 

I am more concerned with modifying the existing code to work with the s332 softdevice. Are there major changes made to the BLE code in the SDK that will need to be accounted for?

Sorry that my original question was so vague!

[Hieu]

No problem.

I am honestly not an expert in ANT and BLE coexistence, and our expert is unfortunately out of office for the coming weeks.
But after a quick look at the ble_ant_app_hrm example, I don't expect major change to the application being necessary. 

What you need to change is mostly in the project setup. You will need to change the global preprocessor, flash and RAM layout, and SoftDevice-specific header and source files.

For SEGGER Embedded Studio, here is a prior case. The particular SoftDevice is different, but the idea is largely the same. Soft device 132 to S112 migration for nRF SDK Blinky example