BLE DFU configuration problem

[JayLynkz]

Hi, 

We want to be able to upload a new firmware in my nrf52832 without serial connection.

I am trying to set up DFU over BLE and I stumbled upon few problems along the way (I am using SES on Windows). 

Starting from the BLE secure DFU bootloader example, after installing the micro-ecc repo in  ...\external\micro-ecc , this error message is raised : 

#error "Debug public key not valid for production. Please see github.com/.../README.md to generate it"

Following the link instructions, I installed nrfutil. Now I would like to know the steps to generate an appropriate key in order to make the example run and add it in my main code !

Thank you very much!

[Hung Bui]

Hi Jerome, 
You would need to generate your own public & private key pair to use the bootloader. The default public key can only be used with the pre-generated images and only for the debug bootloader, not the release one. 
I have a tutorial here that you can follow:  https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader

[JayLynkz]

Hi Hung, thanks for your answer. I'm following the tutorial you mentionned.

 Once I get there, I don't know which option I could use since I'm with SES and it doesn't seem to be a choice in micro-ecc.

[Hung Bui]

Hi Jerome, 
You can have a look at the documentation here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_crypto_backend_micro_ecc.html#lib_crypto_backend_micro_ecc_install
You should use the library .a file in nrf52hf_armgcc . SES use gcc as the compiler. 

[JayLynkz]

Thanks Hung, after following the tutorial, I was able to perform OTA DFU !