• State Verified Answer
  • Replies 3 replies
  • Subscribers 72 subscribers
  • Views 1886 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 116072
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

S132 V2.0 to V3.0 Migration

WestCoastDaz

I have to admit I am lost on the changes required to SDK 11.0 to make the new S132 V3.0 SoftDevice compile.

The migration document talks about the changes but doesn't provide really good context on how to implement them. For example it appears a lot of changes are required to ble_advertising.c and device_manager_peripheral.c.

Does anyone have more details on how to update ble_advertising.c and device_manager_peripheral.c?

I am really hesitant to make significant changes since I don't want to risk introducing bugs into the SDK. In my opinion the purpose of the SDK is to have a known tested, stable base to work from. Introducing a new SoftDevice this way without additional guidance may introduce serious bugs into the SDK.

Thanks, Darren

  • 0

    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.

  • 0 in reply to Einar Thorsrud

    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

  • 0

    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.

Related
Terms of service