NRF52 DFU ZIP Generation

RE: NRF52 DFU ZIP Generation

tesc — Wed, 20 Mar 2019 13:22:45 GMT

Hi,

You find the non-debug BLE DFU bootloader project for the nRF52832 DK at <sdk 14.2 folder>\examples\dfu\bootloader_dfu_ble\pca10040

Regards,
Terje

RE: NRF52 DFU ZIP Generation

ahmdm — Mon, 18 Mar 2019 06:18:55 GMT

Yes i have now disabled this. stuck at the same issue. could you provide me the project so i an build on that?

RE: NRF52 DFU ZIP Generation

tesc — Thu, 14 Mar 2019 12:36:45 GMT

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

RE: NRF52 DFU ZIP Generation

ahmdm — Tue, 12 Mar 2019 11:03:00 GMT

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.

RE: NRF52 DFU ZIP Generation

tesc — Mon, 11 Mar 2019 15:20:26 GMT

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

RE: NRF52 DFU ZIP Generation

ahmdm — Mon, 11 Mar 2019 06:21:02 GMT

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

RE: NRF52 DFU ZIP Generation

tesc — Fri, 08 Mar 2019 15:29:04 GMT

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

RE: NRF52 DFU ZIP Generation

ahmdm — Fri, 08 Mar 2019 06:58:04 GMT

devzone.nordicsemi.com/.../DFBP_5F00_dfu_5F00_BL_5F00_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.

RE: NRF52 DFU ZIP Generation

tesc — Thu, 24 Jan 2019 16:45:26 GMT

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

RE: NRF52 DFU ZIP Generation

zhn — Thu, 24 Jan 2019 15:10:43 GMT

devzone.nordicsemi.com/.../6560.s132_5F00_pca10040.zip

this ia my zip;please check it;

RE: NRF52 DFU ZIP Generation

zhn — Thu, 24 Jan 2019 15:08:51 GMT

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

RE: NRF52 DFU ZIP Generation

tesc — Thu, 24 Jan 2019 11:49:37 GMT

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

RE: NRF52 DFU ZIP Generation

ahmdm — Mon, 14 Jan 2019 05:49:45 GMT

my sdk version is 14.2 (nRF5_SDK_14.2.0_17b948a). I modified the public/private key and the advertising name only. Rest assured is unchanged. I am using bootloader_secure_ble and not the debug version .

Here's the path:

nRF5_SDK_14.2.0_17b948a\examples\dfu\bootloader_secure_ble\pca10040\ses\Output\Release\Exe

RE: NRF52 DFU ZIP Generation

tesc — Fri, 11 Jan 2019 16:31:56 GMT

Hi,

nrfutil 4.0.0 is the latest release, so that is good. What version of the nRF5 SDK are you using?

As I asked previously, have you modified the bootloader in any way?

What bootloader (debug version or not) are you using and from what SDK? (If you provide full path to project file it is easy for me to see what exact version it is.)

Regards,
Terje

RE: NRF52 DFU ZIP Generation

ahmdm — Fri, 11 Jan 2019 07:18:07 GMT

Hi, Thanks for the detailed answer.

I am using nrfutil 4.0.0

RE: NRF52 DFU ZIP Generation

tesc — Thu, 10 Jan 2019 16:24:56 GMT

Hi,

The init file is generated when you generate the zip package, yes.

For an update with just one part (either application, softdevice or bootloader) you should get three files in the zip. There should be a .bin file, which is the binary for the firmware update. There should be a .dat file, which is the init packet. There should be a manifest.json, which states what kind of update it is, and list the bin file and dat file.

For an update with several parts, there will be a .bin and .dat file pair for each part of the update. Then the manifest.json will tell what files belong to what part.

So in short, if you generate the zip package using nrfutil then you should be good. What version of nrfutil are you using?

Regards,
Terje

RE: NRF52 DFU ZIP Generation

ahmdm — Thu, 10 Jan 2019 08:10:49 GMT

I don't know how to generate the init packet. i have found a couple of guide but it isn't clear to me. could you please help. I though the init file is the manifest one when generating the zip

RE: NRF52 DFU ZIP Generation

tesc — Wed, 09 Jan 2019 10:07:11 GMT

Hi,

First, yes, you must perform two separate DFU updates.

INSUFFICIENT_RESOURCES on the bootloader most likely means that the new bootloader is larger than the previous one, so there is not enough space within the flash area designated for the bootloader. Have you modified the bootloader, or are you built the debug version? See the thread Bootloader Update fails (INSUFFICIENT_RESOURCES) for more details.

Regards,
Terje

RE: NRF52 DFU ZIP Generation

ahmdm — Mon, 07 Jan 2019 13:04:39 GMT

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

RE: NRF52 DFU ZIP Generation

ahmdm — Mon, 07 Jan 2019 12:47:35 GMT

Do I have to perform two separate DFU updates then?

RE: NRF52 DFU ZIP Generation

tesc — Mon, 07 Jan 2019 12:44:30 GMT

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