Migrate bootloader from SDK 11 to SDK 13

RE: Migrate bootloader from SDK 11 to SDK 13

bjorn-spockeli — Tue, 14 Nov 2017 12:38:38 GMT

Hi Alex, I was mistaken, the custom bootloader should still have 0x7A000 as the start address. The start address will be changed by the custom bootloader when you update your device with the SD v 4.0.2 + APP + secure BL package.

So the order should be:

build custom bootloader with page alignment fix and legacy to secure workaround by using provided files [here] (devzone.nordicsemi.com/questi...) with 0x7A000 as start address
apply that custom bootloader to my devices
prepare zip package with new SD v 4.0.2 + APP + secure BL

RE: Migrate bootloader from SDK 11 to SDK 13

Alex Takiev — Mon, 13 Nov 2017 10:19:11 GMT

Yes, sure:

$ nrfjprog --family NRF52 --memrd 0x10001014
0x10001014: 0007A000                              |....|

It seems that bootloader address has not been applied to the UICR.

RE: Migrate bootloader from SDK 11 to SDK 13

bjorn-spockeli — Mon, 13 Nov 2017 10:09:51 GMT

Can you use nrfjprog to read the register holding the bootloader start address ( 0x10001014)?

nrfjprog -f nrf52 --memrd 0x10001014

RE: Migrate bootloader from SDK 11 to SDK 13

Alex Takiev — Mon, 13 Nov 2017 10:06:50 GMT

Bjørn,

As you may expect, I've also changed custom bootloader start address in Keil project from 0x7A000 to 0x78000.

RE: Migrate bootloader from SDK 11 to SDK 13

Alex Takiev — Mon, 13 Nov 2017 10:04:33 GMT

Hello Bjørn,

Thank you for your response! I built custom bootloader from the topic you've noticed and create zip package with the bootloader only with nrfutil 0.5.3:

nrfutil dfu genpkg --bootloader custom_bl.hex custom_bl.zip

After I applied it via nRF Connect my device cannot start at all.

RE: Migrate bootloader from SDK 11 to SDK 13

bjorn-spockeli — Mon, 13 Nov 2017 07:52:46 GMT

Hi Alex, you can combine the fix for the page alignment issue with the legacy to secure bootloader workaround, i.e.

build custom bootloader with page alignment fix and legacy to secure workaround by using provided files [here] (devzone.nordicsemi.com/.../), change its address from 0x7A000 to 0x78000 in order to be able to upload the new secure bootloader
apply that custom bootloader to my devices
prepare zip package with new SD v 4.0.2 + APP + secure BL

RE: Migrate bootloader from SDK 11 to SDK 13

Alex Takiev — Sat, 11 Nov 2017 09:34:55 GMT

Hello Bjørn, Thank you for your response. Am I right that I should do following steps:

apply dfu_dual_bank_with_fix.c from this answer to the legacy bootloader which is based on SDK 11
apply that fix by performing DFU of bootloader only
build custom bootloader by using provided files [here] (devzone.nordicsemi.com/.../), change its address from 0x7A000 to 0x78000 in order to be able to upload the new secure bootloader
apply that custom bootloader to my devices
prepare zip package with new SD v 4.0.2 + APP + secure BL

Is it correct?

RE: Migrate bootloader from SDK 11 to SDK 13

bjorn-spockeli — Fri, 10 Nov 2017 23:45:42 GMT

Hi Alex,

Yes, it is possible, but it is not failsafe, see this answer.

Best regards

Bjørn