DFU migration to 14.1

[Lee Daniel Crocker]

I have a bootloader compiled from SDK 14.0, and when I try to upgrade to 14.1, the new linker script (secure_dfu_ble_gcc_nrf52.ld) does not contain the UICR_BOOTLOADER memory region nor the sections that write the values there, so the resulting hex file does not contain instructions to fill in the UICR. Am I supposed to do this myself now? The new script does contain a read-only UICR memory region, and my bootloader doesn't run, so it's clear that those are still being used. They just aren't being set. Should I put the addresses in sdk_config.h or something now? There's no 14 -> 14.1 migration document that I can find, and no comments in the code or Makefiles about the change.

Also, 14 had a short NOINIT region at the end of ram that it shared with the app. Is that no longer necessary?

[Hung Bui]

Hi Lee,

It's just the change of the name, from UICR_BOOTLOADER to uicr_bootloader_start_address in the .ld file

Note that you need to check for the .ld file inside the PCA10040 folder.

Also please be aware that the configuration in the .ld file is only the place holder. The actual writing to flash is done by the code. Please have a look at nrf_bootloader_info.c , we use the attribute keyword to assign a value to the address in the section.

[Lee Daniel Crocker]

Ah, I updated the bootloader code but didn't grab the updated library with it. Now the hex file produced writes to 10001014, but not to 10001018. I suppose bootloader settings page is now hard-coded?

[Hung Bui]

Could you explain that a little bit more ? NRF_UICR_BOOTLOADER_START_ADDRESS is still 0x10001014

"bootloader settings page is now hard-coded": I don't undestand this. BOOTLOADER_SETTINGS_ADDRESS is unchanged between SDK v14 and SDK v14.1 and is 0x0007F000UL.

[Lee Daniel Crocker]

Sorry, my mistake as well. When all the libraries are included, 0x10001018 gets filled in (with 0x7E000, the MBR settings page). Yes, the bootloader settings page is 0x7F000.