DFU upload and signing key with SDK11?

[Shay Ohayon]

Starting SDK 11 (10?) DFU requires a zip file that is being generated with nrfutil. To generate a package you need to supply a private key (generated by nrfutil as well) Is this private key compared to anything in the bootloader supplied with SDK11? I don't see any linking to nrf_svc.h and dfu_init_template_signing.c in the example bootloaders. If this is the case - is the key just ignored?

I'm also having problems uploading packages that were self signed. Here is a way to reproduce the scenario:

1. chip erase (in my case, nrf51822AC - nrf51DK)
2. nrfstudio => flash dfu_dual_bank_ble_s130_pca10028.hex (from SDK11) device should appear as DFU_Targ
3. compile ble_app_hrs/pca10028/s130_with_dfu/armgcc/
4. nrfutil keys generate private.pem
5. nrfutil pkg generate --application nrf51422_xxac_s130.hex --sd-req 0x80,0x87 --key-file private.pem my_package.zip

attempts to upload my_package.zip using nrfToolbox results in the following error "Upload failed: REMOTE DFU operation failed"

uploading of "dfu_test_app_hrm_s130_w_dfu.zip" (from SDK11) works without any problem.

What am I missing? Also, it seems like the size of the provided zip is ~23Kb while my compiled version is 33Kb. Help would be much appreciated!

Thanks,

Shay

[bjorn-spockeli]

Good idea, there will be major changes and improvements compared to the current bootloader. The release is scheduled in the first half of September, subject to change of course.