nRF52 DFU questions

RE: nRF52 DFU questions

Hung Bui — Tue, 23 May 2017 13:40:27 GMT

2.When you tell the bootloader that you are going to update softdevice it won't check for current SD and current application any more, as they will be wiped out.You are correct about the way we receive new softdevice, the application will be erased as the swap region.

3.I see, I was thinking of the bootloader and the bootloader setting as a whole. But yet, they should be taken into account when you calculate the actual max size of the bootloader.

RE: nRF52 DFU questions

Tosa — Tue, 23 May 2017 02:06:15 GMT

Hi Hung,

Regarding:

It turned out to be an issue with my nrf52.cfg file (missing the UICR flash bank); it's okay now.
Just to be sure, the bootloader doesn't know/care about the existing app and SD sizes/start locations? For example, if I update the softdevice, the app would be wiped out regardless of the size of the new softdevice, so that the new softdevice can be stored outside the existing softdevice's flash area before being copied to the proper flash address, correct?
dfu_types.h clarifies that the nRF52 uses two 0x1000 byte pages for BOOTLOADER_SETTINGS_ADDRESS and BOOTLOADER_MBR_PARAMS_PAGE_ADDRESS vs the nRF51 uses one 0x400 byte page for BOOTLOADER_SETTINGS_ADDRESS only, hence the difference in bootloader sizes.

RE: nRF52 DFU questions

Hung Bui — Mon, 22 May 2017 10:53:46 GMT

Hi Tosa,

I dont have experience with OpenOCD. But it seems that this person managed to write to UICR ?

2.Yes you should give enough space because the Secure bootloader from SDK v12 requires more space than the one on SDK v11. To change the start address of the bootloader, have a look here.

3.You are right. The documentation was written when there was no nRF52. It was for 256kB max size flash. If you are using nRF52 with 512kB flash size, the limit is 0x80000.