Maximum possible application size for DFU on the nRF52810

RE: Maximum possible application size for DFU on the nRF52810

aonsquared — Fri, 11 Jun 2021 11:16:22 GMT

I'm also trying to get some more space, and I only need DFU update for the application and not the bootloader/SD.

How do I go about disabling the MBR parameter page?

RE: Maximum possible application size for DFU on the nRF52810

TS Gowtham — Wed, 09 Dec 2020 10:23:48 GMT

Thanks for the answers Einar!

RE: Maximum possible application size for DFU on the nRF52810

Einar Thorsrud — Mon, 07 Dec 2020 11:22:00 GMT

Hi Gowtham,

The BLE SDK examples only use FDS for storing bonding information in the peer manager. If you do not use bonding or pairin and thus do not use the peer manger, then there is no need to include FDS for the sake of any BLE functionality.

(If you use one page for persistent storage using storage then you should make sure to use the page immediately below the bootloader for that, and set NRF_DFU_APP_DATA_AREA_SIZE in the bootloader's sdk_config.h accordingly to only reserve one page.)

Br,

Einar

RE: Maximum possible application size for DFU on the nRF52810

TS Gowtham — Sat, 05 Dec 2020 16:24:46 GMT

Hi Einar,

Thanks for the quick reply and clearing this up. I was able to reduce the size of my application by disabling the logging module and then was able to DFU it.

I would like to clarify one more thing. Are the 3 reserved pages used for anything vital to BLE operation? I am not using bonding in my application. I would like to use 1 page for storing some application data in real time but would like to use only fstorage and not FDS.

Thank

Gowtham

RE: Maximum possible application size for DFU on the nRF52810

Einar Thorsrud — Fri, 04 Dec 2020 13:49:45 GMT

Hi Gowtham,

The limited flash space on the nRF52810 means that it is not possible to update the SoftDevice over OTA DFU, as that has to be done dual bank and there is not enough space in flash for that. You can however update the application over DFU, as that can be done single bank. In that case, the new application will be copied directly in place, and the maximum application size is the space between the end of the SoftDevice and start of the bootloader, less any flash pages used to store application data immediately below the bootloader. See Memory layout.

With S113 version 7.2.0 the SoftDevice size is 112 kB, so the application starts at address 0x1C000. The secure BLE bootloader project typically is 24 kB, and you also need 4 kB for bootloader settings. You can skip the MBR parameter page as you will not do bootloader and/or SoftDevice update.This leaves you with 192 kB - 24 kB - 4 kB - 112 kB = 52 kB if you do not have any persistent application data. If you do, then it will be less.

Also note that unless you have changed the bootloader project, the default configuration reserves 3 pages (12 kB) for application data (such as bonding information). If so, you will not be able to fit your app and a bootloader. In the bootloader this is configured by the NRF_DFU_APP_DATA_AREA_SIZE in it's sdk_config.h file. This should correspond to the configuration of your application, and this matches the default configuration of most applications which use 3 pages for FDS.

Br,

Einar