DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Mon, 14 Oct 2019 09:06:09 GMT

Edvin ,

The issue was solved . The issues is due to the bootloader in our board(DK) .We flashed debug version of SDK14.2 bootloader but the zip file contain non debug bootloder of SDK 15.3 that's why its not advertising .

when we flashed non debug version bootloder of SDK 14.2 to DK its working fine.

Thanks for your reply so far

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 11:43:31 GMT

Does it advertise if you just program the bootloader and softdevice manually, using nrfjprog?

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 10:34:50 GMT

I will send you the zip take a look at by your self if you can .I will also unzip it.

devzone.nordicsemi.com/.../15.3sd_2B00_bootloader_5F00_sd.zip

And look the nrfutil command below for generating zip

nrfutil pkg generate --bootloader secure_bootloader_ble_s132_pca10040.hex --bootloader-version 2 --hw-version 52 --sd-req 0x9D --sd-id 0xB7 --softdevice s132_nrf52_6.1.1_softdevice.hex --key-file my_secret_private_key.pem 15.3sd+bootloader_sd.zip

Look the below screen short these what i saw when i unziped

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 10:16:58 GMT

What changes did you do to your bootlaoder? Try to unzip the SDK again, so that you know that you didn't change any of the settings.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 09:01:26 GMT

That is the problem man . Its not advertising .

How can i debug the code after OTA-DFU i don't known it.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 08:53:42 GMT

[quote user="NANDHU NAKULAN"]Is the DK advertise as "DfuTrag " from new bootloder which is updated through OTA or not.[/quote]

Yes. The "DfuTarg" is from the new bootlaoder. You can confirm this by changing the advertising name of the bootloader if you open the bootloader project from SDK15.3.0, and go into sdk_config.h, and look for:

#define NRF_DFU_BLE_ADV_NAME "DfuTarg"

Change it to

#define NRF_DFU_BLE_ADV_NAME "Dfu15"

Or something else (not too long).

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 08:28:29 GMT

Just tell me one thing Edvin.

If a DK contains only SD and BL of sdk 14.2 and its advertising as "DfuTrag"

Then using nRF_Connect desktop application we done a OTA -DFU to that DK .

The zip file used for OTA-DFU contains SD and BL of sdk 15.3.

After the OTA -update reaches 100% (ie transfer completed) what will happen to DK?

Is the DK advertise as "DfuTrag " from new bootloder which is updated through OTA or not.

[quote userid="26071" url="~/f/nordic-q-a/53114/doubt-in-zip-file-generation-for-ota--dfu/214526"]If the signature changes it means that the bootloader will reject the application. [/quote]

Actually there is no application is using man . please try to understand.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 08:22:05 GMT

You can debug the application using the "pca10040_ble" bootloader project as long as you program the bootloader settings, and use "attach debugger" instead of "build and debug".

The difference between "attach debugger" and "build and debug" is that "build and debug" will upload the .hex file. When you do this from the IDE, the application will behave the same, but there are some bit differences. If there are any bit differences it means that the signature of the application will change(the signature generated when you create the DFU image or if you generate the bootloader settings and program it manually).

If the signature changes it means that the bootloader will reject the application.

So use "attach debugger".

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 08:07:16 GMT

[quote userid="26071" url="~/f/nordic-q-a/53114/doubt-in-zip-file-generation-for-ota--dfu/214514"]If it is not advertising as DFU targ, then there is probably a bug in your application that causes the chip to reset before it starts advertising.[/quote]

Actually there is no application in the DK only SD and BL and also there is no application hex in the zip file too.

You mean the application for bootloader ?

[quote userid="26071" url="~/f/nordic-q-a/53114/doubt-in-zip-file-generation-for-ota--dfu/214514"]Do you remember the ticket where I told you about debugging when there is a bootloader present?[/quote]

yes, But at that time, debug was done by you and told me to use "pca10040_ble" instead of "pca10040_ble_debug".

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 07:42:06 GMT

If it is not advertising as DFU targ, then there is probably a bug in your application that causes the chip to reset before it starts advertising. Do you remember the ticket where I told you about debugging when there is a bootloader present?

In Segger Embedded Studio, you can just press "Tools" -> "Attach Debugger" from the toolbar menu when you have your application project open, and it will start the debug session.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 07:20:42 GMT

[quote userid="26071" url="~/f/nordic-q-a/53114/doubt-in-zip-file-generation-for-ota--dfu/214502"]And you managed to do this but it turned out your application was too big. Did you change to the 512kb version of the nRF?[/quote]

Yes man ,I changed it to 512kb .

I will send both hex file both softdevice and bootloader hex file to you take look

softdevice hex

devzone.nordicsemi.com/.../6052.s132_5F00_nrf52_5F00_6.1.1_5F00_softdevice.hex

bootloader hex

devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble_5F00_s132_5F00_pca10040.hex

After flashing bootloder and softdevice the flash memory layout look like below

And its advertising as "DfuTrag" too.

Please check by yourself man that the bootloader is fit for 512 kb and also try to make a zip file with all the condition i mentioned and try to upload to a DK which is flashed with SD and BL of sdk 14.2.

In our case after doing the OTA -DFU its not advertising . i don't known why.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Fri, 11 Oct 2019 06:59:05 GMT

Hello Nandu,

I believe we discussed this in another post, didn't we?

And you managed to do this but it turned out your application was too big. Did you change to the 512kb version of the nRF?

However, I may repeat myself if that is what you want. I also told your colleague this, by the way.

[quote userid="76730" url="~/f/nordic-q-a/53114/doubt-in-zip-file-generation-for-ota--dfu/214487"]What is nrfutil command for generating a zip file containing SD and BL(sdk 15.3) at these condition. Mainly i need to known what is value of "--sd-req and --sd-id"[/quote]

if you intend to upgrade from SDK14.2.0 to SDK15.3.0 with DFU, in other words, you move from S132v5.0.0 to S132v6.1.1, you need the "--sd-req 0x9D --sd-id 0xB7.

Ask your colleague. We have gone through this in detail. If you are not sure who I am talking about, send me a PM, and I can give you his name.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

NANDHU — Fri, 11 Oct 2019 04:10:09 GMT

hi edvin ,

Conisder the below condition .

We have a development kit of NRF52832(512 KB FLASH).
we flashed the softdevice(s132_nrf52_5.0.0_softdevice.hex ) and bootloader (secure_dfu_ble_s132_pca10040_debug.hex) into it .
i.e both softdevice and bootloader is from sdk 14.2.
After flashing SD+BL to DK the DK is advertising as "DfuTrag".
Now we need to to update a zip file through OTA containing softdevice and bootloder from sdk 15.3 into it .

Doubts

What is nrfutil command for generating a zip file containing SD and BL(sdk 15.3) at these condition. Mainly i need to known what is value of "--sd-req and --sd-id"
These is the Softdevice hex "s132_nrf52_6.1.1_softdevice. hex" and these is the bootloader hex "secure_bootloader_ble_s132_pca10040.hex" from SDK 15.3. if you need its hex please ask.

we you can please reply the command for generating SD+BL zip file with all the condition mentioned above.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Edvin — Thu, 10 Oct 2019 13:24:40 GMT

As Hadi says, you need to add the arguments that are required to generate the DFU image.

These are common:

nrfutil pkg generate --sd-req 0xXX --hw-version 52 --key-file private.key "DFU_image_name".zip

Then if your image contains an application, you need to add:

--application application.hex --application-version N

If your image contains a bootloader, you need to add:

--bootloader bootloader.hex --bootloader-version N

if your image conatins a softdevice, you need to add:

--softdevice softdevice.hex --sd-id 0xYY

The links that Hadi linked to describes it quite well. Also, if you type "nrfutil pkg generate --help" you will see a description of all possible input parameters.

RE: DOUBT IN ZIP FILE GENERATION FOR OTA -DFU.

Hadi Deknache — Thu, 10 Oct 2019 12:39:04 GMT

Hi Nandhu,

You run following commands to generate an unsigned package:

1. nrfutil pkg generate --softdevice softdevice.hex dfu_package.zip

2. nrfutil pkg generate --bootloader bootloader.hex dfu_package.zip

3. nrfutil pkg generate --softdevice softdevice.hex --bootloader bootloader.hex dfu_package.zip

4. nrfutil pkg generate --softdevice softdevice.hex --bootloader bootloader.hex --application app.hex dfu_package.zip

Example on a signed package:

nrfutil pkg generate --hw-version 52 --application-version 1 --application application.hex --sd-req 0x98 --softdevice softdevice.hex --bootloader bootloader.hex --key-file private.key app_bl_sd_dfu_package.zip

Useful links for further reading:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfutil%2FUG%2Fnrfutil%2Fnrfutil_pkg.html

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader

/Hadi