regarding DFU

RE: regarding DFU

roger.k — Wed, 19 Apr 2017 06:02:37 GMT

No problem

RE: regarding DFU

bjorn-spockeli — Wed, 19 Apr 2017 05:57:17 GMT

Happy to help :) I would appreciate if you could mark the answer as correct/accepted by clicking the checkmark in the circle to the left of the answer.

RE: regarding DFU

roger.k — Wed, 19 Apr 2017 05:10:21 GMT

Thank you very much for your help. It's so great!

RE: regarding DFU

bjorn-spockeli — Tue, 18 Apr 2017 08:50:38 GMT

Hi Roger,

Q1: You can create combined images, e.g. SoftDevice+Bootloader, by combining the --application, --softdevice and --bootloader options. The allowed combinations are shown in the table below and is also displayed in nrfutil's documentation found here.

So if you want to create a SoftDevice+Bootloader firmware image you use the following command

nrfutil pkg generate --hw-version 52 --sd-req 0x98 --bootloader-version 0x11 --bootloader boot.hex --softdevice s132_nrf52_4.0.2_softdevice.hex --key-file priv_0407.pem sd_boot_dfu_package.zip

Q2: The secure bootloader (SDK v12.x.x and later) will perform a dual bank updates if there is enough space, otherwise it will perform a single bank update, see this Infocenter page. You can configure the bootloader to only perform dual bank update, i.e. you will get an error at the start of the DFU process if the image is to large.

In your specific case, the S132 v4.0.2 requires 0x0001F000 bytes (124kB) and the bootloader requires 0x5000 bytes (20kB), this leaves you with 368 kB (512kB - 124kB - 20kB). This means that you can perform a dual bank update of your application if its 368kB/2 = 184 kB. The combined SD+BL image is only 144kB, so you will be able to update the SoftDevice and bootloader without the application being erased as long as the application is not larger than 368-144kB = 224kB. However, I expect that the SoftDevice size will increase as we release newer versions so it is always wise to leave some space to account for this.

Bjørn

RE: regarding DFU

roger.k — Mon, 17 Apr 2017 07:21:26 GMT

Thank you so much for your help.

For Q1, How can I make image files(*.zip file)? I want to know about NRFUTIL's Option after [nrfutil pkg generate].

For Q2, I'm using DFU example code. I think it's supporting dual bank mode. Right? And there should be memory area to save old files. Could you tell me the size and the area of memory for saving old files? I actually want to know how big size files can be downloaded through OTA.

I need your help.

RE: regarding DFU

John — Fri, 14 Apr 2017 15:29:44 GMT

Hello,

For Q1, you can use the mergehex utility that Nordic provides as part of its nRF5 toolset installation.

For Q2, the answer is a bit more nebulous. If you have the memory, you can use the DFU in its dual bank mode in which case the new application is downloaded before the old application is erased so a failure usually results in the old application remaining available. If you don't have the memory, you have to use single bank mode and the old application is erased before the new application is transferred to your device. Note, soft device DFU erases the application IIRC.