S132 V2.0 to V3.0 Migration

RE: S132 V2.0 to V3.0 Migration

Einar Thorsrud — Wed, 31 Aug 2016 11:34:53 GMT

I see. We do not have more detailed instructions than what you can find in the migration document at the moment. SDK 12 will have full support for S132 v3.0.0 and will probably be released soon. Unless you for some reason must port your application to S132 v3.0.0 immediately, I suggest waiting for the new SDK.

RE: S132 V2.0 to V3.0 Migration

WestCoastDaz — Tue, 30 Aug 2016 15:32:34 GMT

Einar,

Thank you for the reply. I am using the IAR tool chain and I have changed the IROM1 start address to 0x1F000 that's not my problem. My problem is implementing the changes to ble_advertising and other SDK files.

Also, as a start I am implementing this in the Nordic example HRS project.

Thanks, Darren

RE: S132 V2.0 to V3.0 Migration

Einar Thorsrud — Tue, 30 Aug 2016 06:46:17 GMT

The amount of changes needed depend on your application. In most applications you will only need to change the start address of your applications flash, as the flash usage of the SoftDevice has changed. (In Keil that means that you have to change IROM1 Start from 0x1C000 to 0x1F000. If you use GCC you need to change the flash ORIGIN in the linker script in the same way.)

If you use LL Privacy or want any of the other new or significantly changed features, you should follow the migration document in more detail. In that case you might also consider wait for the next SDK release, which will include support for S132 v3.