Secured DFU Bootloader Compilation

[David K.]

Dear Nordic Team and Community,

I am trying hard to compile and run the bootloader_secure example provided in SDK12.1. Here is the steps I follow :

• Compilation runs smoothly and as a result I have a HEX file. I am using the same key as provided in the example

Linking target: _build/nrf52832_xxaa_s132.out

text data bss dec hex filename

33816 144 8368 42328 a558 _build/nrf52832_xxaa_s132.out

• I create the bootloader_settings.hex.

• I merge (using mergehex) the nrf52832_xxaa_s132.hex, bootloader_settings.hex and s132_nrf52_3.0.0_softdevice.hex to create the HEX I am installing on my nrf52.

The device is installed and the LED3 is lit.

However, I can't perform any DFU. The Android nrfConnect stops with an error Remote DFU error: REMOTE DFU OPERATION FAILED.

My point is that with provided hex file everything runs smoothly.

Also, my final hex file is 442kB whereas the provided one is 445kB.

I am missing some magic somewhere.

I would appreciate some hints, help or solution.

Thanks,

David

[bjorn-spockeli]

If you're not testing with the example images from the SDK, then you have to generate your own private-public key pair with nrfutil.

[David K.]

Thanks for the hints. I believe this not the point. I have generated all myself. At the end, I have successfully managed to perform a secured DFU not really following the tutorial. I have not merged any HEX file. I still need to push my tests further to check that bootloader_settings is taken into account when security checks are performed.

[bjorn-spockeli]

Could you describe what you did in order to perform a Secure DFU that was not mentioned in the tutorial?If there's an error in the tutorial then I will correct it ASAP.

[David K.]

Dear Bjørn, I will for sure share my experience. I need some time to be sure of what I am writing so that no errors arise when people try.

[bjorn-spockeli]

Great :) It will be very useful for other DevZone users.