Add MCUBoot and OTA over BLE with private key

[ekidsalan123]

Hi, 

I'm currently trying to add MCUBoot in my project.

The project was built successfully by adding these lines to prj.conf.

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

The memory report clearly indicates that MCUBoot has been successfully flashed onto my board.

I also can see DFU funtion and SMP service work in nrf connect APP.

Here are my questions:

1. How can I use a private key with currently settings?

2. How to update the firmware by using new nRF Connect SDK DFU? More precisely, what files should I prepare for?

[Sigurd Hellesvik]

Hi,

See https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/, lesson 8.
Also https://webinars.nordicsemi.com/adding-device-firmware-update-5

Regards,
Sigurd Hellesvik

[ekidsalan123]

Thank you for providing the answers to my questions.

After generated the private key, what need to do for using private key is adding this line in CMakeLists.txt

set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE \"${CMAKE_CURRENT_SOURCE_DIR}/priv.pem\")

And put priv.pem file in project folder(out from build folder)

[Sigurd Hellesvik]

I dont understand the question.
Could you rephrase it?

[Madhu Mohan Reddy]

Hi,
I am working on nRF52840 using nRF Connect SDK.
I don't know how to generate private key for DFU OTA over BLE
Can you suggest any source To implement DFU OTA over BLE using private key for my application

In Dev Tutorial its not mentioned about private key and webinar is not accessing.
Thank you in advance.

[ekidsalan123]

Hi,

please take a look here

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_signature_keys.html