Migrating from SDK9 to SDK12

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Tue, 06 Dec 2016 10:40:00 GMT

I just tested this and the Secure bootloader starts after the DFU has finished. Have set the BOOTLOADER_START_ADDR of the secure bootloader to 0x39000 like you did in the legacy bootloader?

RE: Migrating from SDK9 to SDK12

johnny — Tue, 06 Dec 2016 10:10:52 GMT

Yes. If I use the nRFgo Studio to update the bootloader(24K) and SD, the bootloader(24K) can boot up success. But When I use the bootloader(16K) upgrade to bootloader(24K) by DFU, after the DFU the bootloader(24K) can't boot up success. Can you try this?

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Tue, 06 Dec 2016 09:21:05 GMT

Hi Johnny, I set the memory settings in the dfu_gcc_nrf51.ld to

FLASH (rx) : ORIGIN = 0x39000, LENGTH = 0x6C00

and set BOOTLOADER_REGION_START to 0x39000. I flashed the generated hex file to a nRF51 DK along with the S130 v2.0.1 SoftDevice and execution is passed to the bootloader without any issues.

RE: Migrating from SDK9 to SDK12

johnny — Mon, 05 Dec 2016 07:06:21 GMT

Hi, I modify the dfu_gcc_nrf51.ld: from FLASH (rx) : ORIGIN = 0x3C000, LENGTH = 0x3C00 to FLASH (rx) : ORIGIN = 0x39000, LENGTH = 0x6C00 No, I can't able to debug the bootloader.

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Mon, 05 Dec 2016 06:41:27 GMT

Hi Johnny, have you to edited the linker settings to reflect the changes made to BOOTLOADER_REGION_START, i.e. FLASH (rx) : ORIGIN = 0x39000, LENGTH = 0x6C00? Are you able to debug the bootloader?

RE: Migrating from SDK9 to SDK12

johnny — Mon, 05 Dec 2016 01:20:57 GMT

hi Bjørn, in my question 2, I changed the BOOTLOADER_REGION_START from 0x3C00 to 0x3900 to make the enough space to keep SDK12 bootloader. But if I do that, the bootloader can't boot up success. Can you help to check it? Thanks.

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Fri, 02 Dec 2016 15:14:27 GMT

Yes, you are correct. As long as the BOOTLOADER_REGION_START is set to 0x3AC00 and you adjust the size of the application accordingly you should be able to update the SDK v9.0.0 bootloader to the SDK v12.0.0 bootloader. You do not have to alter the BOOTLOADER_SETTINGS_ADDRESS, just leave it at 0x3FC00. The disadvantage is that you have (24-15kB) 9kB that are unused until you update to SDK v12.0.0.

RE: Migrating from SDK9 to SDK12

Alex — Fri, 02 Dec 2016 15:02:13 GMT

Am I correct that in order to make SDK 9 bootloader future compatible with SDK 12 bootloader I will only need to recompile it with new BOOTLOADER_SETTINGS_ADDRESS and BOOTLOADER_REGION_START and restrict application ROM to BOOTLOADER_REGION_START? We are using SDK 9 and not planning to move to SDK 12 but may do at some point.

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Fri, 02 Dec 2016 14:45:08 GMT

Sorry, that was for the nRF52. I have corrected the addresses to be valid for the nRF51 in my answer.

RE: Migrating from SDK9 to SDK12

Alex — Fri, 02 Dec 2016 14:25:20 GMT

Is 0x0007A000/0x78000 for nRF51 or nRF52?

RE: Migrating from SDK9 to SDK12

bjorn-spockeli — Fri, 02 Dec 2016 13:52:54 GMT

In order to update the bootloader from SDK v11.0.0 or older (now referred to as Legacy) to the bootloader in SDK v12.x.0 ( referred to as Secure) you have to ensure that the start address of the legacy bootloader that is flashed to your devices is identical to that of the new Secure Bootloader as this cannot be changed at runtime on the nRF51x22 without erasing the entire chip and reflashing it.

The default start address of the legacy bootloader is 0x0003C000, while the default start address of the Secure bootloader is 0x3AC00, i.e. the legacy bootloader start address must be set to 0x3AC00 so that there is room for the new Secure bootloader.

Thus, if the start address of the legacy bootloader that is flashed to the devices that you want to update set to 0x3C000, then it is not possible to update from the legacy bootloader to the secure bootloader beacuse there is not enough room for the new bootloader.

Best regards

Bjørn