Related articles

1.《【Nordic】nRF52810 OTA upgrade ( One )–DFU Environment building 》
2.《【Nordic】nRF52810 OTA upgrade ( Two )–DFU How to use 》
3.《【Nordic】nRF52810 OTA upgrade ( 3、 ... and )–DFU The theoretical analysis 》

1. Preface

This article is based on 《【Nordic】nRF52810 OTA upgrade ( One )–DFU Environment building 》 On the basis of , To achieve DFU OTA Upgrade firmware functions .

2. Generate micro_ecc_lib_nrf52.lib library

Nordic In the use of DFU Conduct OTA Upgrade will use ECC Verify the certified firmware , So in DFU The project needs to produce micro_ecc_lib_nrf52.lib.

1. Download the last article micro-ecc-master Copy the source code to SDK In the catalog external\micro-ecc in , And rename to micro-ecc
   
   

2. open Cygwin Command line
   

3. cd To micro-ecc Project directory ：nRF5_SDK_17.0.2_d674dde\external\micro-ecc\nrf52nf_keil\armgcc
   

4. perform make command
   
   Because I didn't find it here gcc An error is reported in the tool , Modify file ：nRF5_SDK_17.0.2_d674dde\components\toolchain\gcc\Makefile.windows
   take

   GNU_INSTALL_ROOT := C:/Program Files (x86)/GNU Tools ARM Embedded/9 2019-q4-major/bin/
   GNU_VERSION := 9.2.1
   GNU_PREFIX := arm-none-eabi
   

   It is amended as follows gcc Actual installation directory ：

   GNU_INSTALL_ROOT := D:/Program Files (x86)/GNU Arm Embedded Toolchain/10 2020-q4-major/bin/
   GNU_VERSION := 10.2.1
   GNU_PREFIX := arm-none-eabi
   

   Re execution make, Compile successfully .
   
   

3. Generate dfu_public_key.c And add

1. Generate private key
   stay D Create a new folder on disk , Name it key, stay cmd Enter the following in the command ：nrfutil keys generate D:\key\private.key Instructions , Generate private key file private.key
   

   Be careful ： To save the private key private.key, Every new firmware upgrade in the future , You must sign through this private key first , Once lost ,DFU Will not be able to

2. Generate public key
   Enter the generate public key instruction ：nrfutil keys display --key pk --format code D:\key\private.key --out_file public_key.c
   
   Produce public keys on the desktop public_key.c
   
3. Add the public key to the project
   Public key public_key.c Renamed as dfu_public_key.c, And replace the directory with this file nRF5_SDK_17.0.2_d674dde\examples\dfu Under the dfu_public_key.c
   

4. compile bootloader

Because I use here nRF52810 platform , So choose dfu bootloader Path as follows ：
nRF5_SDK_17.0.2_d674dde\examples\dfu\secure_bootloader\pca10040e_s112_ble\arm5_no_packs

Compile successfully ：

5. burn bootloader and SoftDevice hex file

Use jlink burn bootloader and SoftDevice：

• burn bootloader
  nRF5_SDK_17.0.2_d674dde\examples\dfu\secure_bootloader\pca10040e_s112_ble\arm5_no_packs\_build\nrf52810_xxaa_s112.hex
• burn SoftDevice
  nRF5_SDK_17.0.2_d674dde\components\softdevice\s112\hex\s112_nrf52_7.2.0_softdevice.hex

After burning , Installed by mobile phone nRF ConnectAPP Search for BLE, appear DfuTarg It means that we have entered bootloader Pattern . Because there is no burning application hex, So I entered directly bootloader Pattern .

6.nRF Connect APP Conduct OTA upgrade

upgrade application The firmware of is the firmware compiled by the previous project ：nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_uart\pca10040e\s112\arm5_no_packs\_build

• Make OTA Upgrade package
  nrfutil pkg generate --hw-version 52 --application-version 1 --application nrf52810_xxaa.hex --sd-req 0x0103 --key-file D:\key\private.key dfufile.zip
  

• take OTA Upgrade package dfufile.zip Copy to cell phone

• Connect BLE DfuTarg
  

• Click on the DFU Small icons , choice ZIP file dfufile.zip
  

• Upgrading …
  

• Upgrade success , appear application ble The name of Nordic_UART, Here's the picture ：
  

7. Errors occurred

• error 1

  ..\..\..\..\..\components\libraries\crypto\backend\micro_ecc\micro_ecc_backend_ecc.h(52): error:  #5: cannot open source input file "uECC.h": No such file or directory
    #include "uECC.h"
  ..\..\..\..\..\components\libraries\bootloader\dfu\nrf_dfu_validation.c: 0 warnings, 1 error
  

  error analysis ：
  Prompt not found uECC.h The header file
  terms of settlement ：
  Reference resources 2. Generate micro_ecc_lib_nrf52.lib library We can solve this problem .

• error 2

  compiling dfu_public_key.c...
  ..\..\..\dfu_public_key.c(20): error:  #35: #error directive: "Debug public key not valid for production. Please see https://github.com/NordicSemiconductor/pc-nrfutil/blob/master/README.md to generate it"
    #error "Debug public key not valid for production. Please see https://github.com/NordicSemiconductor/pc-nrfutil/blob/master/README.md to generate it"
  ..\..\..\dfu_public_key.c: 0 warnings, 1 error
  

  error analysis ：
  There is no effective dfu Encrypt public key
  terms of settlement ：
  Reference resources 3. Generate dfu_public_key.c And add We can solve this problem .