NRF52 DFU ZIP Generation

[ahmdm]

Hi,

I want to be able to update the bootloader along with the application via OTA DFU. I know I can't generate both the application and bootloader in one image/zip so I have to make two different zip packages. 

I can't find any guide on how to do that. Please help out. 

[tesc]

Hi,

Then you must make two different zip packages, one for the bootloader and one for the application. Then do the updates after each other, first bootloader then application.

Regards,
Terje

[ahmdm]

i get this error:

DFU failed with error: When writing 'EXECUTE' command to Control Point Characteristic of DFU Target: Operation code 4 (EXECUTE) failed on DFU Target. Result code 4 (INSUFFICIENT_RESOURCES).

I made the zip for the bootloader using this command:

nrfutil pkg generate --hw-version 52 --bootloader-version 2 --bootloader secure_dfu_ble_s132_pca10040.hex --sd-req 0x9D --key-file private.key app_dfu_bootloader.zip

[tesc]

Hi,

I am very sorry for the long delay.

That should be the correct location.

Can you attach the hex file and the zip file, so that I can have a look at them to see if anything is wrong?

Regards,
Terje

[zhn]

SDK 11 nrfutil 4.0.0;i have the same question;please help;3q

[zhn]

6560.s132_pca10040.zip

this ia my zip;please check it;

[tesc]

Hi,

SDK 11 used an older version of DFU, so this is not the same question.

For legacy DFU you should use an older version of nrfutil, see the README.md for nrfutil on github.

Regards,
Terje

[ahmdm]

DFBP_dfu_BL_package.zip

I am sorry for the extreme delay. Here's the bootloader image i made. Please give it a view if possible and let me know.

[tesc]

Hi ahmdm,

The number of flash pages set aside for the bootloader cannot increase during DFU, so the new bootloader must be within the settings used for the old one. For the bootloader example the limitat is at 24 kB, which is 24576 bytes (0x6000 in hexadecimal.) I see from the zip packet that the size of your new bootloader is 24896 bytes (0x6140 in hexadecimal), so you are overshooting by 320 bytes.

You might be able to get under 24 kB in size by increasing the optimization level (or set it to optimize for size.) If that is not enough, or you are already getting the smallest possible build, then you have to either remove something from the project or to set aside more space for the bootloader in the first place.

Regards,
Terje

[ahmdm]

could you kindly suggest how to increase the optimization level and also increase the size of the bootloader?

[tesc]

Hi,

What toolchain do you use?

In SES you find the "Optimization Level" setting under Code -> "Code Generation" in the project options. For other toolchains it is typically also in an option tab.

For adjusting flash settings, see Adjustment of RAM and Flash memory. Please note that you need the flash settings for the bootloader not to change when upgrading using DFU. (I.e. old and new bootloader must have the same start address and size in flash.)

For more on flash placement, see the Memory layout section of the bootloader library documentation.

Regards,
Terje

[ahmdm]

I am using Segger Embedded Studio (SES). the optimzation has been set for size so i believe setting it to level 3 or 2 won't make a difference. 

I can't figure out how the size would change since I actually haven't changed anything apart from the advertising name just to know the difference. That is it. 

Seems to me that I am at fault with the zip generation of the bootloader i guess. 

[tesc]

Hi,

The bootloader projects ending in _debug are larger than the non-debug versions. Are you using the non-debug version of the bootloader in both instances, and made sure not to enable any logging?

Regards,
Terje