What is the DFU different in sdk 12.3 and sdk10

[Vincent]

Hi, I just try DFU function in sd130/sdk12.3 and it does work very well. I did: (1).Generating your own key: nrfutil.exe keys generate priv.pem

(2).Display a public key from your key file nrfutil.exe keys display --key pk --format code priv.pem > public_key.c

(3).nrfutil.exe pkg generate --hw-version 51 --sd-req 0x87 --application-version 1 --application Nordic_HRM.hex --key-file priv.pem hr_dfu_app.zip

(4).nrfutil.exe settings generate --family NRF51 --application Nordic_HRM.hex --application-version 0 --bootloader-version 0 --bl-settings-version 1 HR_BL_SET.hex

(5).mergehex --merge nrf51_bootloader_s130.hex HR_BL_SET.hex --output M_HRbootloader.hex

and I use nRFgo update sd and bl and app to MCU and use IOS nRF ToolBox can update other I modify new FW_App.

But I also have some project which use sd310 in sdk10. Now I need implement DFU function to my old project.

My question is how to use old dfu funtion and what is different step with new dfu.

Thanks

[bjorn-spockeli]

Hi Vincent,

the bootloader with signing from SDK v10.0.0 was an experimental implementation and is not intended for use in a final product.

The production-ready implementation of our Secure DFU bootloader was added in SDK v12.3.0, but this SDK does not support the S310 (The last SDK that supports it is SDK v10.0.0).

Migrating the S310 project to SDK v12.3.0 should be possible, but it will involve compiling the S130 secure bootloader project againt the S310 headers and the API has changed a lot from the S310(based on the S110 v8.0.0 API) so there might be a lot of conflicts.

I think the easiest solution is to use the Legacy S110 Dual Bank Bootloader from SDK v10.0.0 and compile that against the S310 headers. You wont be able to sign the firmware images, but its by far the path of least resistance. How to add Legacy DFU support to your S310 application is explained on this Infocenter page.

Bjørn

[Vincent]

Ok, I will think about how to move sd310 project to sdk 12.3.

Thanks