Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

RE: Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

Jeremy Hubbard — Mon, 25 Aug 2014 14:00:00 GMT

After copying the custom code into the ble_app_hrs example it started working as expected.

RE: Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

Stefan Birnir Sverrisson — Mon, 25 Aug 2014 13:51:49 GMT

My experience is that it is easier to copy custom code from SDK v5.2.0 into similar code template in version 6.0.0, than to actually try to port your code. This is mainly because the bond-manager in version 5.2.0 is replaced by the device-manager in version 6.0.0, see release notes for nRF51 SDK v6.0.0.

RE: Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

Lucas — Fri, 22 Aug 2014 15:24:41 GMT

Stefan,

Is this truly the easiest way to do it? I was going to attempt to look through the release notes and migration document, but if you feel this is the best method I will proceed that way. Can you link me to the latest version of the ble_app_hrs example. I don't know where that is located.

RE: Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

Hailang — Wed, 20 Aug 2014 06:28:46 GMT

These resources may also help:

<s110_nrf51822_7.0.0_releasenotes.pdf> and <s110_nrf51822_7.0.0_migration-document.pdf> in the s110_nrf51822_7.0.0.zip
The chapter "Changes:" in <release_notes.txt> of SDK 6.0.0.

Changes:

- Added partial support for Keil 5 uvprojx files.

ANT
    - None
    
ANT + BLE (Dual stack)

BLE
    - New module device manager replaces bond manager for storing persistent data
    - Experimental device manager support for s120 (BLE central)
    - S110 serialization solution has been reworked
        - 100% s110 BLE APIs are now serialized
    - S110 support for application concurrent multiprotocol radio access
    - Pstorage module: Added API for doing range updates 
    - Experimental: Device firmware upgrade now supports updating both softdevice and bootloader for s110
    
Proprietary
    - Enhanced ShockBurst: Added nrf_esb_reuse_pid() function to API, giving "reuse payload" functionality.
    - Gazell: Added "suspend" mode enabling sharing of radio and PPI. 
    - Gazell: HW resources are released when Gazell is being disabled or entering suspend mode.
    - Gazell: HW resources are reconfigured when Gazell is being enabled or exiting from suspend mode.

ps, these crossed my mind because of enlightenment from Stefan's help on one of my question. Thanks to Stefan.

RE: Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

Stefan Birnir Sverrisson — Tue, 19 Aug 2014 13:48:57 GMT

Hi Jeremy

We do not provide any guide on how to port your code between major nRF51 SDK releases. The method that is generally used to port custom application between major nRF51 SDK releases is to copy the custom code, block by block, into a similar example in the new SDK. For example, if I had made a custom application based on the ble_app_hrs example, I would copy the custom code into the ble_app_hrs example in the new SDK.

Also, SD 7.0.0 is only compatible with SDK 6.0.0 and SD 6.0.0 is only compatible with SDK 5.2.0