how to generate the public key for nrf52 DFU? Unable to install nrfutil.exe on my windows 7

[Nitesh]

How to generate the Public keys to firmware application?

Even i am unable to install the nrfutil.exe for my windows 7? what could be the issue?

Tried pip install for the nrfutil-6.0.1.tar.gz using  command line "c:\ pip install ./downloads/nrfutil-6.0.1.tar.gz" still unable to install. Always getting below message

Please help me on nrfutil installation and public key generation for the DFU.

Nitesh

[Vidar Berg]

Hi,

It looks like the connection is timing out for some reason. Please try to use the nrfutil executable included in the release instead: https://github.com/NordicSemiconductor/pc-nrfutil/releases

Best regards,

Vidar

[Nitesh]

I tried downloading the nrfuitl.exe, but its not installing. Scree shows the command line execution, but not installing.

On command line tried nrfutil --version, nothing is showing

[Nitesh]

thanks i will check and get back to you.

Thanks again for helping me

[Nitesh]

Hi,

I am able to create the public and private key

Then clone the micro_ecc to external\mcc_ecc folder

Then copied the public_key.c file to "C:\NextGenHMI-Project\nRF5_SDK_16.0.0_98a08e2\examples\dfu"

Then opened the project "C:\NextGenHMI-Project\nRF5_SDK_16.0.0_98a08e2\examples\dfu\secure_bootloader\pca10056_s140_ble_debug\ses"

Note : i am using PCA1056 board and Soft device S140 and using SDK v16.0.0 for IDE SES

Please let me know how to compile the microECC library now?

Struck with this step, whether i need to add the files to project and then i need to compile?

i am seeing no micro_ecc folder in my project structure

Need help in building the library

Thanks in advance

Nitesh

[Vidar Berg]

The PCA10056 configuration does not depend on uECC crypto library because it uses the cc310 instead.

[Nitesh]

Then what we have to do for support the secure Bootloader for our product? Please let me know how to make the secured firmware upgrade using existing secure Nordic bootloader.

How to make DFU compatible with secure nordic bootloader?

Really confused which crypto to use in application/bootloader?

As per my knowledge Nordic Secured BL has uECC already running in it and we have to make the make the our firmware package with public key so that BL will first decrypt and then load the application. Please correct me if i am wrong.

So if we need to use CC3100 as per PCA10056 then we need to change the BL crypto algorithm?

Do you have any example code for PCA10056 DFU with CC3100?

Just need to make the secure BL to make it work with our PCA10056 board, its very urgent need, Can you guide how to approach this?

Thanks in advance

Nitesh  

[Vidar Berg]

Nitesh said:

So if we need to use CC3100 as per PCA10056 then we need to change the BL crypto algorithm?

Nitesh said:

Do you have any example code for PCA10056 DFU with CC3100?

 cc310 is selected by default when you are targeting the 52840.  It provides HW acceleration for the crypto operations used during DFU, unlike the uECC library that implements everything in SW (=slower). The reason uECC is mentioned in the blog post is that cc310 HW is not available on our other chip variants in the nRF 52 family. 

Nitesh said:

Just need to make the secure BL to make it work with our PCA10056 board, its very urgent need, Can you guide how to approach this?

 Follow the steps in the blog post, but ignore the part about uECC.

[Nitesh]

U mean uECC library clone and copy to local project folder i need to ignore?

[Vidar Berg]

Yes. You don't need the uECC because you are using the nRF52840

[Nitesh]

In that case, BL also need to change or i can use as it is from example?

So to do DFU (i.e. only application upgrade), so package with signature need to built using nrfutil.exe or just add signature by including public_key.c in my application code before DFU process?

Please guide me.

[Vidar Berg]

No. The bootloader example is already configured to use the cc310. Please follow the quide.