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

Parents
  • 0

    If you want to use the one without _debug, you need to state all the versions requirement needed, as mentioned in this.

    Here is the commandline script I used:

    Generate private key:

    nrfutil keys generate priv.pem

    Generate public key:

    nrfutil keys display --key pk --format code priv.pem --out_file public_key.c

    Genrate package (this is only for S132 v3.0):

    nrfutil pkg generate --hw-version 52 --sd-req 0x8c --application-version 1 --application ble_app_hrs.hex --key-file priv.pem app_dfu_package.zip

    Note the --hw-version should be either "52" for nRF52832/40 or "51" if you use nRF51 chip. You can however, change this if you want your own hw-version code by modifying the bootloader to add NRF_DFU_HW_VERSION define in your code. For testing, I suggest you to stick to the "52". This is a little bit tricky part because in the documentation we have an example using "--hw-version 1" which can cause trouble if testing without adding NRF_DFU_HW_VERSION define.

Reply
  • 0

    If you want to use the one without _debug, you need to state all the versions requirement needed, as mentioned in this.

    Here is the commandline script I used:

    Generate private key:

    nrfutil keys generate priv.pem

    Generate public key:

    nrfutil keys display --key pk --format code priv.pem --out_file public_key.c

    Genrate package (this is only for S132 v3.0):

    nrfutil pkg generate --hw-version 52 --sd-req 0x8c --application-version 1 --application ble_app_hrs.hex --key-file priv.pem app_dfu_package.zip

    Note the --hw-version should be either "52" for nRF52832/40 or "51" if you use nRF51 chip. You can however, change this if you want your own hw-version code by modifying the bootloader to add NRF_DFU_HW_VERSION define in your code. For testing, I suggest you to stick to the "52". This is a little bit tricky part because in the documentation we have an example using "--hw-version 1" which can cause trouble if testing without adding NRF_DFU_HW_VERSION define.

Children
No Data
Related
Terms of service