Updating bootloader + SD from SDK13 to SDK14

RE: Updating bootloader + SD from SDK13 to SDK14

bjorn-spockeli — Fri, 17 Nov 2017 11:49:23 GMT

You should get an Insufficient resources error if you try to update to a bootloader that will not fit in the old bootloader region, see this infocenter page.

RE: Updating bootloader + SD from SDK13 to SDK14

Aaron — Thu, 16 Nov 2017 18:03:02 GMT

Also, it would be nice if the bootloader would refuse to flash a bootloader that is too large to fit in flash. As it is now you can brick the device by sending it a bootloader that is too large to fit.

RE: Updating bootloader + SD from SDK13 to SDK14

Aaron — Thu, 16 Nov 2017 17:58:26 GMT

If you look at secure_dfu_gcc_pca10040_debug.ld in examples/dfu/bootloader_secure_ble, the ORIGIN changed from 0x75000 to 0x73000 between SDK13 and SDK14. If I try to compile our SDK14 bootloader_secure_ble with ORIGIN 0x75000, I get linker error: _build/nrf52832_xxaa_s132.out section .text' will not fit in regionFLASH' region `FLASH' overflowed by 2620 bytes

RE: Updating bootloader + SD from SDK13 to SDK14

bjorn-spockeli — Thu, 16 Nov 2017 08:58:09 GMT

Yes, it is correct that the old and the new bootloader must have the same start address, i.e. the new bootlaoder must be able to fit within the region occupied by the old bootloader. However, the SDK v13.0.0 and the SDK v14.0.0 bootloaders should be the same size, given that its non-debug to non-debug or debug to debug.

RE: Updating bootloader + SD from SDK13 to SDK14

Aaron — Wed, 15 Nov 2017 17:15:09 GMT

The problem was definitely the UICR, it seems that it is not possible to update from an old bootloader to a new bootloader if the new bootloader is larger. In general it seems like updating from one SDK to a newer SDK is something that's not well supported or tested. But if you think you might do it, be sure to pad out the space taken by the bootloader in case the next bootloader is larger. In my case we got it working by going from the SDK13 debug bootloader to the SDK14 non-debug bootloader.

RE: Updating bootloader + SD from SDK13 to SDK14

bjorn-spockeli — Fri, 27 Oct 2017 13:11:06 GMT

No, the workaround must only be implemented in the new bootloader as the issue is that its trying to verify that the copy operation was successful by comparing the swap area with the bootloader region, but due to the increased SD size it performs the compare operation with a 0x4000 offset.

RE: Updating bootloader + SD from SDK13 to SDK14

Aaron — Thu, 26 Oct 2017 01:04:09 GMT

So, I updated the new bootloader to SDK 14.1.0, and set NRF_DFU_WORKAROUND_PRE_SDK_14_1_0_SD_BL_UPDATE which supposedly fixes this problem but I'm seeing the same result. I'm a bit confused. Is this code getting executed in the existing SDK13 bootloader, or in the one that's being uploaded? Do I need to upload an SDK13/SD4 bootloader with this workaround code first, and then upload an SDK14/SD5 bootloader?

RE: Updating bootloader + SD from SDK13 to SDK14

Justin — Wed, 25 Oct 2017 20:49:22 GMT

There's a known issue for SDK14 that might be the reason devzone.nordicsemi.com/.../

devzone.nordicsemi.com/.../