dfu_application.zip content

[Gabriele]

Hi,
working with NCS v1.4.2, I see building products for an <app> landing into subfolder <app>/build/, in several flavours

app_moved_test_update.hex
app_signed.hex
app_test_update.hex
app_to_sign.bin
app_update.bin
merged.hex

There is an additional file
dfu_application.zip
which contains
- app_update.bin
- manifest.json

Is the zipped file allowed to be arbitrarly populated ?
For example, how to make the system to include merged.hex into archive ?

[Simon]

The app_update.bin file will be used to update the application, and should get put into the secondary flash, so if you have another image that should get placed e.g. after your application, you can merge it with app_to_sign.bin and then sign it yourself. I think that should work fine.

I'm not too familiar with manifest.json files and dfu_application.zip. Also I'm not sure if you are able to use a hex file instead of a binary file, then you would need to convert it to binary format before putting it into the secondary flash.

What does your merged.hex file contain? Does it contain the mcuboot? Is your goal to update both the mcuboot as well as the application? Please tell me if that is the case and I will instruct you how to achieve this.

It would be useful if you can give me some more information about your setup. What is your final goal? What images do you want to merge, and update? Why are you using the dfu_application.zip instead of just the .bin file directly?

Best regards,

Simon