Latest status of Buttonless secure DFU in SDK 13.0

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Tue, 13 Jun 2017 08:26:21 GMT

@bswimley: We didn't continue to implement bond forwarding. The explanation was posted here: devzone.nordicsemi.com/.../ Please scroll till the last quote in Italic.

RE: Latest status of Buttonless secure DFU in SDK 13.0

bswimley — Mon, 12 Jun 2017 21:04:18 GMT

Hi, Has there been any progress on this issue with SDK 13? I see that you had indicated something happening in the March or April time frame. Like Sam, we would like to support sharing bonding between the app and the DFU.

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Fri, 05 May 2017 09:18:59 GMT

Could you open a new case and give all description there ? please try to test with only BL+SD first.

RE: Latest status of Buttonless secure DFU in SDK 13.0

Srikar — Thu, 04 May 2017 15:23:47 GMT

@Hung Bui,Means Bootloader IROM starting address 0x78000 and size 0x6000 is same in SDK 13.0 and 12.0.2. In my case DFU update (secure BL+SD+APP) from 12.02 to 13.0 is failing even other private keys are same but DFU updates are working for without issues from 12.0.2 to 12.0.2 and 13.0 to 13.0 .

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Thu, 04 May 2017 14:43:59 GMT

@Srikar: What do you mean by "As Bootloader address is not changed" ? It is changed in our current example in SDK v13.

I don't see any problem update bootloader+SD+APP from SDK 12.0.2 to SDK 13.0.0.

RE: Latest status of Buttonless secure DFU in SDK 13.0

Srikar — Thu, 04 May 2017 13:28:23 GMT

Hi, As Bootloader address is not changed,Can I update bootloader+SD+APP from SDK 12.0.2 to SDK 13.0.0?

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Wed, 22 Mar 2017 13:12:34 GMT

@Sam: To change the address, it's pretty simple and already done in our DFU bootloader inside gap_params_init() , see gap_address_change() function.

Regarding bond forwarding, I don't know when it will be officially included. But we tech support will try to come up with an example. I hope to have something ready by the end of this month or first week April.

RE: Latest status of Buttonless secure DFU in SDK 13.0

sam wagner — Tue, 21 Mar 2017 19:06:21 GMT

Thanks Hung!

Is there plan to include support for sharing Bond Info between Application and Bootloader during DFU? If yes, when would it be available?

Is there any example that shows how to change the address of the device when switching from Application to Bootloader?

Regards, Sam

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Thu, 16 Mar 2017 14:46:01 GMT

We don't support bond forwarding yet. But is it a firm requirement that the link has to be re-encrypted when you do DFU ?

If it's OK to do DFU with an open link ( still secure DFU, just no bond) you can think of changing the address of the device when it switches to bootloader.

This also require you to modify the DFU app on the phone to look for the new address after it write the command to tell the application to switch to the bootloader.

If encryption is the requirement, you may have to think of writing some code to forward bond information and re-use it after you switch to bootloader. You can refer to what we have in the bootloader in SDK v11 to know how to do it.

RE: Latest status of Buttonless secure DFU in SDK 13.0

sam wagner — Wed, 15 Mar 2017 23:19:22 GMT

Hi Hung,

Thanks for the information. As far as I know, SDK12 does not support the sharing of BLE link encryption key between the bootloader and the firmware application.

Does SDK13 support a case where [1] Central and Device are bonded using BLE encryption (say JUST WORKS) and [2] Phone App triggers DFU by writing into the DFU endpoint, thereby making the Device switch to bootloader mode, [3] then the phone App transfers signed DFU image over the air to the device, and [4] the Device jumps to the new image after that?

We need to support the above scenario ASAP for our production code.

Regards, Sam

RE: Latest status of Buttonless secure DFU in SDK 13.0

Hung Bui — Tue, 14 Mar 2017 11:57:08 GMT

Hi Sam,

Compare to SDK v13 alpha, the buttonless example in the SDK v13 official doesn't change much.

It is still in experimental mode
Some issues on SDK v12 and 13 alpha were fixed such as the characteristic's write property missing, the bootloader_setting section missing were fixed.
Now we use RAM retention register GPREGRET to set the flag to enter bootloader mode instead of writing to flash.
Change the service's UUID to the Secure-DFU UUID
Change from the DFU control point property from notification to indication
Requires nRFutil v2.2.0