• State Verified Answer
  • Locked Locked
  • Replies 31 replies
  • Subscribers 73 subscribers
  • Views 12057 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 118528
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Zip file failed to upload for ble_secure project

Newbie

Hello, I am working on ota ble_secure project. I have created a zip file which is the last step and copied this file to my smart phone so that I can upload it using nrf toolbox. The upload fails. I am not sure which files to include to create a zip package. I am attaching my zip package as well as the files that I used to merge.app_dfu_package.zip. The hex file is nrf52832_xxaa_s132.hex.

The log file of error is log.txt

Sdk which I have is www.nordicsemi.com/.../nRF5-SDK

I am using this project in sdk sdknordic\examples\dfu\bootloader_secure\pca10040

Left side is new sdk and right side is old sdk. bootloader.PNG

Log file New Text Document.txt

New log file errorlog.txt

  • 0

    Hi,

    Please add more information on the SDK version you use, how you generate the .zip file

    What error you have when the updating failed ? You can find a log file using nrfLogger app

  • 0

    I am using nrf51latest13alpha this sdk and in that I am trying ble-secure given in examples. It says dfu process failed. I dont know hot nrf logger works. I am generating my zip file by using the commands nrfutil pkg generate --debug-mode --application (location of hex file and file is attached) --key-file (location of my .pem file) app_package.zip.

    Thanks,

  • 0

    Have you updated the bootloader with your public key ?

    Have installed nRFLogger on your phone ? You should be able to find the trace inside that app.

    You can also test with the test .zip file inside test_image_update_nrf52, when you test that you would need to use the debug bootloader project with the original key.

  • 0

    I am following pcbreflux.blogspot.in/.../nrf51822-secure-dfu-ota-via-ble.html this project. I did everything given here including updating the public key. I am faing challenge in generating zip package. In the following command nrfutil pkg generate --debug-mode --application dfu_app.hex --key-file ../my_secret_private_key.pem app_package.zip where will I find the hex file for this project? Currently I used the hex file generated in build and I think they are using some other file to generate. I have uploaded dual_bank_ble_s132 firmware in my nrf52. Do I need to make changes in that project? I uploded this so that it starts advertising and I can see dfutarg in my nrfconnect app. Thanks,

  • 0

    Hi,

    You can also follow the instruction in our documentation here.

    The dfu_app.hex is the hex that you generate when you compile your application.

    I assume you have updated the public key in the bootloader , compiled it and used that bootloader.

    You would need to tell me how it failed when doing DFU. The nRFLoger would help. Or you would need to capture a sniffer trace when you do the process.

    In addition, you can enable NRF_LOG in the DFU bootloader so that it will print UART log when doing DFU.

Related
Terms of service