update softdevice,bootloader and app

[Jim]

      I now want to update the program in SDK14.2 to SDK15.2 through DFU, so softdevice, bootloader, app need to be updated, how should I operate?
      I first try to update the bootloader and softdevice into an upgrade package, and then upgrade the app to an update package, but when upgrading the bootloader and softdevice, nrf52832 enters the bootloader and displays "Error: Insufficient resources".
      The upgrade package generated by nrfutil is as follows(priv.pem as same as old):
      Nrfutil pkg generate --hw-version 52 --sd-req 0xA5 --sd-id 0xAF --bootloader-version 3 --bootloader bootloader.hex --softdevice sd.hex --key-file priv.pem dfu_package_blsd_V1.zip
      Start nrfutil pkg generate --hw-version 52 --sd-req 0xA5 --application-version-string 0.4.00 --application app.hex --key-file priv.pem dfu_app_V1.zip

       In addition, when updating the app, the version of the application must be larger than before?

[Vidar Berg]

Hi,

The error indicates that the new image is too large. Does the new and old bootloader have the same start address in FLASH? Note that the debug version of the bootloader is bigger than the release version.   

In addition, when updating the app, the version of the application must be larger than before?

No, but you're not allowed to downgrade if NRF_DFU_APP_DOWNGRADE_PREVENTION is set to '1' in your sdk_config.h file. Please see nrf_dfu_ver_validation.c->fw_version_ok() if you want to see how the check is implemented.  

[Jim]

New and old bootloader not have same start flash address.In the bootloader I used the app timer.sdk15.2 which seems to need more flash space or it will compile incorrectly. How do you handle updates in this case？

[Vidar Berg]

Hi,

Could you upload both the new and old bootloader hex file here so I can check it here? Also, which chip are you using, is it 52832 xxAA? 

[Jim]

i use 528bootloader_old.hexbootloader_new.hex32 xxAA

[Vidar Berg]

The new bootloader starts at address 0x77000 while the old one started at address 0x78000. Please change the start address in your new bootloader to 0x78000 and see if you get the same result.