update softdevice,bootloader and app

RE: update softdevice,bootloader and app

Vidar Berg — Fri, 10 May 2019 12:19:05 GMT

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.

RE: update softdevice,bootloader and app

Jim — Fri, 10 May 2019 10:25:07 GMT

i use 528devzone.nordicsemi.com/.../bootloader_5F00_old.hex devzone.nordicsemi.com/.../bootloader_5F00_new.hex32 xxAA

RE: update softdevice,bootloader and app

Vidar Berg — Fri, 10 May 2019 08:57:38 GMT

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?

RE: update softdevice,bootloader and app

Jim — Thu, 09 May 2019 13:25:43 GMT

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？

RE: update softdevice,bootloader and app

Vidar Berg — Thu, 09 May 2019 12:54:22 GMT

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.

[quote user=""]In addition, when updating the app, the version of the application must be larger than before?[/quote]

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.