I am working on secure dfu. I followed all the steps mentioned in this post and successfully created the secure .zip file.
Here's what I did(In this order):
Here's what is happening:
It'd be fantastic if you can help me understand what's going on here and tell me how to fox this.
If I use the .hex file from /project/pca10056/blank/ses/Output/Debug/Exe and create a secure .zip file with nrfutil and try to upgrade the application, the upgrade is complete on nRF Connect App. Then LEDs will be off and nothing happens. On restart, nothing boots up - neither BLE nor new App code.
You should use ble_app_blinky_pca10056_s140.hex under nRF5_SDK\examples\ble_peripheral\ble_app_blinky\hex to create the .zip file to run the BLE application.
Thank you for responding to my question. I have my own project(Without BLE) and I want to understand how to use DFU to update the application.
As you know already, Everytime I "build" the application using SES, a new .hex file will be created in:
Can you please tell me what should I do, apart from creating update package using nrfutil, to update this application using nRFCOnnect app on my phone?
Here are the steps I currently follow:
I think I get what you're saying.
I believe, I am not creating "Application" file. Creating the zip files using the .hex file from nRF5_SDK_16.0.0_98a08e2\examples\peripheral\projectName\pca10056\blank\ses\Output\Release\Exe, is not the right way to creating "Application" which bootloader is expecting.
If my understanding is correct, can you please help me create a right application file to be used in secure USB and/or secure BLE bootloaders?
I think you are testing secure_bootloader_ble, then you only can update the ble application like BLE Blinky Application.
If you want to update the application like Blinky Example, you should use the UART DFU.