[SDK] Switching our project from SDK12.2 to SDK14.0

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

Bjørn Kvaale — Tue, 12 Dec 2017 11:53:25 GMT

Great to hear! Thanks for updating this case! :)

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

trdop — Mon, 11 Dec 2017 09:57:17 GMT

On this issue, the Nordic engineer recommended and informed me that: The bootloader does not use the nrf_sdh_ble_default_cfg_set() function while enabling the stack, so the sdk_config configuration is not applied, and the softdevice seems to enable SC by default.

so for those who have this issue, add the following else statement in ble_stack_init [ nRF5_SDK_14.2.0_17b948a/components/libraries/bootloader/nrf_ble_dfu.c ] :

#if defined(NRF_DFU_BLE_REQUIRES_BONDS) && (NRF_DFU_BLE_REQUIRES_BONDS == 1)
    NRF_LOG_DEBUG("Running Service Changed config");
    ble_gatts_cfg_service_changed.gatts_cfg.service_changed.service_changed = 1;
    err_code = sd_ble_cfg_set(BLE_GATTS_CFG_SERVICE_CHANGED, &ble_gatts_cfg_service_changed, ram_start);
    VERIFY_SUCCESS(err_code);
    NRF_LOG_DEBUG("Finished running Service Changed config");
#else
    NRF_LOG_DEBUG("Running Service Changed config");
    ble_gatts_cfg_service_changed.gatts_cfg.service_changed.service_changed = 0;
    err_code = sd_ble_cfg_set(BLE_GATTS_CFG_SERVICE_CHANGED, &ble_gatts_cfg_service_changed, ram_start);
    VERIFY_SUCCESS(err_code);
    NRF_LOG_DEBUG("Finished running Service Changed config");
#endif

It works very well on several tests on my side!

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

Bjørn Kvaale — Mon, 04 Dec 2017 13:58:44 GMT

Hi trdop. Sorry for the delayed response. I have taken a look at your question for a while now and am unsure as to why this issue is occurring. I think it is best if you post this question on Nordic Mypage (you can link to this devzone question in your mypage question). Have a nice day!

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

trdop — Wed, 29 Nov 2017 14:22:14 GMT

to follow up and report an important blocking point, before me putting that on MyPage…

————> I took the last example of IOS-Pods-DFU-Library v 4.0.3 with that I make sure my BL SD APP + (settings 4 Factory) v.12.2 -> V.12.2 without problem: OK

————> I took a simple example ANCS v.14.2 and I grafted DFU with that I get my BL SD APP + (Settings 4 Factory) v.14.2 -> V.14.2 without problems: OK

————> now when I want to make the OTA of my device in the nature that are on the SDK 12.2 So BL SD APP + (Factory Settings 4) v.12.2 -> ANCS + DFU V.14.2

This is what happens: (see in screenshots: animated GIF)

1st pass: OK
2nd pass: NOK > "Error 305: Writing to characteristic failed!"

Do you have ideas, because before advancing more in the migration I would naturally test and validate it in the state! and also I saw in the bootloader sdk_config.h v14.2 option BOND what it is?, it is set to false but if I put it to true what will concretely change? I have a little trouble understanding, in that case?

In any case if you can help me or give me a track to follow about the error with characteristic not written when DFU it would be great! Thank you

What I find odd too is when I use the latest version, to make my OTA from 12.2 to 14.2 with "nRF Connect.app" on iOS, instead of my Adapted IOS-Pods-DFU-Library example to make the OTA, it's directly puts a message alert that can not find DFU Service? and don't even go in the 1st pass which was "working" at least previously with IOS-Pods-DFU-Library example, would it be a source of ideas ?

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

Bjørn Kvaale — Wed, 22 Nov 2017 12:39:30 GMT

Good idea! Good luck! And just update this post or create a new case if you run into problems.

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

trdop — Wed, 22 Nov 2017 12:19:51 GMT

Thank you both for these interesting and encouraging returns I will actually go to version 14.2 directly!

I think it should be okay to be attentive, to tell the truth the most scary thing is this Bootloader story and memory slot allocation !

@Bjørn, after I use the DK52 , but now I turn on our device that was built around the nRF52 also

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

Bjørn Kvaale — Wed, 22 Nov 2017 10:28:52 GMT

I agree with @Aaron , I would definitely upgrade to SDK 14.1. You can read up about a bug on SDK 14 here. Just curious, are you using nrf52 dk's as your devices? Also agree that the DFU process can be tricky, so think hard before you start. If you really need the OTA DFU Buttonless feature, it would be a good idea to upgrade, as the 14.1 version is more stable than the one found in SDK 12.2. If you decide to start, give it a try & you can either update this thread or create a new case on devzone if you run into problems.

RE: [SDK] Switching our project from SDK12.2 to SDK14.0

Aaron — Mon, 20 Nov 2017 17:05:45 GMT

SDK 14.1 has a fix for a bug that would otherwise prevent you from updating the SoftDevice, so you'd definitely want that one. Also, make sure your new bootloader fits in the same size as the old one, the UICR bootaddr can not be changed. Also, be aware that updating the SDK is a more painful process than you might think, they do not make changes backwards compatible. Not a Nordic Engineer, but recently gone through the process of updating to SDK 14.1. Although looking at it recently there is a 14.2 out now, I supposed you'd want to update to that.

When using the buttonless DFU service in 14.1, there is a second, undocumented init function you have to call or else recent nRF Connect iOS update will not be able to update your device. See devzone.nordicsemi.com/.../