OTA DFU NRF5340

[kumanan]

Hi,

The below is our requirement for NRF5340

1. we have a DFU application with bootloader as an hex file

2. we have another app say blinky as an hex file

3. merge these two hex files and create a new hex file - using 

nrfutil pkg generate --hw-version 53 --application-version 1 --application ble_app_blinky_pca10056_s140.hex --sd-req 0xA9 --key-file private.key app_dfu_package.zip

4. using NRF connect in mobile load this merged hex file and flash it 

We are getting conflict in step 3

Please help us resolve this issue

[Simonr]

Hi

1. I'm not sure I understand the question. DFU means Device Firmware Upgrade, so it is the update. Are you asking if you need to update the bootloader every time you do DFU as well? That should not be necessary I think.

2. That is possible, but you'll need a device connected to the cloud that can get the firmware from the cloud onto the nRF53. This could for example be a phone, where you can use the DFU library for Android / iOS to send FW to your device, and the .zip could be gotten from the cloud for example. We don't provide any Android / iOS cloud-example for DFU. I assume different cloud companies have example code how you download things from the cloud to your smartphone app.

Best regards,

Simon

[kumanan]

Hi Simon,

Let me explain this item 1

i understand that bootloader is updated into boot slot

I am not sure about SMP server - where it is getting loaded

i want to upgrade my app alone say Blinky1, Blinky2, Blinky3, Blinky4

what i need to include extra code/ config  here? for boot and smp server to work, so that i can upgrade any number of times

Item 2. - idea is to automatically upgrade and get feedback whether the upgrade is successful

the system architecture is as below video ref

https://www.youtube.com/watch?v=bluz8uC7WEs

regards

Kumanan