• State Verified Answer
  • Locked Locked
  • Replies 31 replies
  • Subscribers 73 subscribers
  • Views 13691 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

    Yes, please do, just follow the instruction.

  • 0

    Hello, I got error as unknown 8202. Log file is attached above.

  • 0

    Hi,

    Please describe every steps you did when testing. Which SDK version you are using, why you use s132_nrf52_2.0.1_softdevice.hex ? It's old softdevice, not for SDK v12 or 13.

    Have you generated your own key pair and have you updated the public key to the bootloader or you use the debug bootloader without update ? Please list all your steps as detailed as possible.

  • 0

    Hello Hung,

    1. I uploded new softdevice file which is given in examples\dfu\ble_dfu_send_hex\test_images_update_nrf52840\dfu_test_softdevice_s140.hex

    2. Generated the keys using nrfutil keys generate my_secret_private_key.pem . For this I installed the necessary libraries.

    3. Updated the new keys in dfu_public_key. I just changed the keys which i got and edited the file with my keys.

    4. Then I compiled the project. Load it in my nrf52 device.

    5. It started advertising nrftarg as described above.

    6. Now prepared the zip file as descibed above in debug mode with the command as follows nrfutil pkg generate --debug-mode --application dfu_app.hex --key-file ../my_secret_private_key.pem app_package.zip

    7. Copied the zip file to my phone.

    8. Now I am trying to upload this zip file using nrftool box app.

  • 0

    dfu_test_softdevice_s140.hex is not the softdevice for nRF52832, it's for nRF52840.

    Have you ever tested or familiar with any of the nRF52832 application in the SDK ? Have you tested with normal application, for example ble_app_hrs ??

    You should flash the hex file in \components\softdevice\s132\hex instead.

    What was the dfu_app.hex you used ? You generated the file from your application or it's an example in the SDK, I suggest to use an example in the SDK.

    Which bootloader project you used, the one with _debug surfix or the non-debug one ?

    What was the "unknown 8202" issue you mentioned ?

    Btw, tell me the exact version of the SDK you are using.

Related
Terms of service