How to generate init file(*Dat) for secure DFU OTA update?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Wojtek — Thu, 13 Apr 2017 08:16:23 GMT

Create separate question, as it has nothing in common with .dat generating problem.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Thu, 13 Apr 2017 07:57:13 GMT

Hello Sir,

Greetings of the day!!

Thanks for your valueble suggestion in OTA now i am trying interface another device with UART of my nRF51 Dk board. For that i connect it with p9 and p11 (rx & tx pins).

Now how can i UART0 for communication?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Hung Bui — Thu, 30 Mar 2017 09:11:52 GMT

@Nilesh: please open the unmodified DFU bootloader in SDK v11, look for Project Option -> Utilities-> Use externalTool for Flash Programming. You can find it.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Wed, 29 Mar 2017 16:33:37 GMT

Hello Sir,

Thank you for your quick response.

Can you explain me how to set nrfjprog in keil for programming?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Hung Bui — Wed, 29 Mar 2017 14:21:52 GMT

You can use KEIL to flash the bootloader, just make sure nrfjprog was used in Keil for programming.

If you want to flash the application without doing OTA DFU, you can flash it directly with Keil, but since the bootloader will check a bootloader setting to know if there is a valid application is available. We need to overwrite the bootloader setting. Please have a look at section E in this FAQ.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Wed, 29 Mar 2017 09:56:19 GMT

Hello Sir,

Thank you for your valuable response.

As per your suggestion, i am trying to update hex file of ble_app_blinky_c program with SDK11. And I have done successfully OTA update file in my nRF51 Board.

But as of Now, every time i need to upload softdevice & bootloader file using nrfgo studio then after its updates hex file.

So, Is it possible bootloader and hex file using keil? Any additional changes required into the program?

Thanks

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Wed, 29 Mar 2017 07:14:21 GMT

Hello Sir,

I apologize for the mistake.

I am trying to OTA with the SDK11 and SDK12 both.

When i an trying with SDK 11 and start to transferring process using my mobile app.(NRF Connect), my mobile application start to transferring process and completed it by 100% but no any effect happened in my board.

Same thing with in SDK 12, my mobile application given me error message "DFU is failed".

Thanks

RE: How to generate init file(*Dat) for secure DFU OTA update?

Hung Bui — Tue, 28 Mar 2017 14:23:05 GMT

I still don't understand what you are describing.

Could you explain more clear what you meant here: With SDK11, my updating process will completed by firmware in not update and in SDK12, not process shown in application directly close the update process.

Note that if you are using mbed, make sure your image is without the softdevice (shadow platform). You may want to upload your .hex file and the .zip file you generated.

If you are doing DFU update for SDK v12, there is a lot of requirement regarding secure DFU. Please have a look here to know how to test it.

Please state clearly which bootloader did you use ? Did you use FOTA bootloader from mbed or the DFU bootloader in our SDK ?

To make it easier, I would suggest you to use the bootloader from SDK v11.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Tue, 28 Mar 2017 14:11:07 GMT

Hi Sir,

Today, i am trying with the ble_app_blinky_c program in keil which is located into the nRF5_SDK_12.2.0_f012efa\examples\ble_central\experimental\ble_app_blinky_c\pca10028\s130\arm5_no_packs.

Simply, i build the project and using generated hex file create the zip file using "nrfutil pkg generate --debug-mode --application your_application.hex --key-file key.private app_dfu_package.zip"

Now when i am trying to update the firmware, the mobile application shown "DFU is failed" error message.

Please suggest me. thanks

RE: How to generate init file(*Dat) for secure DFU OTA update?

Hung Bui — Mon, 20 Mar 2017 10:19:11 GMT

@Nilesh: I'm sorry it's been a long discussion. But we need to you tell us what exactly you want to do now. What is "this" in "How can i implement this with keil?"

If you still have a problem with .dat file (which you don't need, simply generate the .zip file, it's easier) please try to use : nrfutil pkg generate --debug-mode --application your_application.hex --key-file key.private app_dfu_package.zip

And let us know what kind of problem do you have. The your_application.hex is the hex file you get when compiling with Keil.

You should update the bootloader with the public key match with your private key that you generate.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Mon, 27 Feb 2017 05:39:04 GMT

Dear Sir,

How can i implement this with keil? Any example file availble in SDK?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Fri, 17 Feb 2017 13:00:32 GMT

Yes, i had done with dfu_test_app_hrm_s130.zip Can you suggest me any example file for testing DFU with own generated package?

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Fri, 17 Feb 2017 12:47:20 GMT

Can you perform a successful DFU with the dfu_test_app_hrm_s130.zip image ?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Thu, 16 Feb 2017 10:31:10 GMT

I am using dfu_test_softdevice_s130.hex for softdevice and dfu_test_bootloader_s130.hex for bootloader which is located in above path which you are mentained. and trying to update DFU using dfu_test_app_hrm_s130.hex file with own generated package.

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Wed, 15 Feb 2017 12:57:08 GMT

The zip file size should not matter. Have you tried using the default(i.e. unaltered secure bootloader) and performed an update with the test images in the examples\dfu\ble_dfu_send_hex\test_images_update_nrf51 folder? I am afraid that questions regarding the mbed implementation of our bootloader/DFU service should be posted on the mbed forums as we mainly support the nRF5x SDKs.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Fri, 10 Feb 2017 10:50:29 GMT

Also i am trying to generate my own hex file for DFU OTA in mbed tool with shadow platform. First i am trying with BLE_LED example and select shadow platform. So, is there require any extra line into the code? Unfortunately it's also not working for me.

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Fri, 10 Feb 2017 10:44:05 GMT

Hi,

Thank you for your reply.

But this command is also not working for me.

Also, I analysed that the example zip file size is 30,816 bytes and my zip file size is 30,870 bytes.

So, i hope it's doesn't matter.

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Fri, 10 Feb 2017 09:27:08 GMT

If you do not want to upload the hex files or the image you created then I suggest that you try to create a debug package, i.e.

nrfutil pkg generate --debug-mode --application dfu_test_app_hrm_s130.hex --key-file key.private app_dfu_package.zip"

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Thu, 09 Feb 2017 08:47:30 GMT

No, First i burn softdevice and bootloader hex using nRfgo studio then generate the zip package using above steps for update the application.

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Wed, 08 Feb 2017 08:47:12 GMT

Ok, can you attach the bootloader hex, application hex and the zip package that you created to the question `?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Wed, 08 Feb 2017 06:35:13 GMT

Thank you for your quick response.

I am using nRF Connect with android version 4.4.2.

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Tue, 07 Feb 2017 15:02:05 GMT

Are you using the nRF Connect or the nRF Toolbox app? Which type of phone is it, android or iOS?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Tue, 07 Feb 2017 14:58:41 GMT

First i am maintain dfu_public_key.c file in same folder and update it using update command which mentioned in earliest reply.

I am not getting any error but when i am trying to update it using my mobile app, first showing connecting dfu message then intializating DFu then not strart updating process but directly display disconnecting message.

So, just disconnecting after the connecting without any error message.

RE: How to generate init file(*Dat) for secure DFU OTA update?

bjorn-spockeli — Tue, 07 Feb 2017 13:47:14 GMT

Can you elaborate when you say it does not work? Do you get an error message from the app your using to perform DFU? Did you replace the Debug Public key in the bootloader source code with the one you generated from the private key?

RE: How to generate init file(*Dat) for secure DFU OTA update?

Nilesh Bhavsar — Mon, 06 Feb 2017 15:48:27 GMT

Thank you for the reply.

I am tried to generate same package using dfu_test_app_hrm_s130.hex located into nRF5_SDK_12.2.0_f012efa\examples\dfu\ble_dfu_send_hex\test_images_update_nrf51.

These are the setup which i am followed: 1: First generate the .pem file using "nrfutil keys generate private.pem" 2: Export into dfu_public_key.c using "nrfutil keys display --key pk --format code private.pem --out_file public_key" command. 3: Generate zip file "nrfutil pkg generate --hw-version 51 --sd-req 0x87 --application-version 1 --application dfu_test_app_hrm_s130.hex --key-file key.private app_dfu_package.zip"

But it's not working. Then, compare information of the both packages using "nrfutil pkg display package.zip" command attached herewith.

C:\Python27\Scripts>nrfutil pkg display dfu_test_app_hrm_s130.zip

DFU Package: <dfu_test_app_hrm_s130.zip>: | |- Image count: 1 | |- Image #0: |- Type: application |- Image file: nrf51422_xxac.bin |- Init packet file: nrf51422_xxac.dat | |- op_code: INIT |- signature_type: ECDSA_P256_SHA256 |- signature: 5dc00acac037cc2ee6bf997d5112ddd6827ed7ffaca278d7e5cb402a82ba 0124bf69ea1b9da6c5b3aa8b571d7eb5c4855a664b4408840115fc84f69c168c17c9 | |- fw_version: 0x00000001 (1) |- hw_version 0x00000033 (51) |- sd_req: 0xCAFE, 0x87 |- type: APPLICATION |- sd_size: 0 |- bl_size: 0 |- app_size: 30176 | |- hash_type: SHA256 |- hash: b4767e557c167df5a78f2e1e380b5181879094b1e6819965eb7499e079a8269e | |- is_debug: True

C:\Python27\Scripts>nrfutil pkg display app_dfu_package.zip

DFU Package: <app_dfu_package.zip>: | |- Image count: 1 | |- Image #0: |- Type: application |- Image file: dfu_test_app_hrm_s130.bin |- Init packet file: dfu_test_app_hrm_s130.dat | |- op_code: INIT |- signature_type: ECDSA_P256_SHA256 |- signature: aa00bab4f4ce5dca5d95e2837967a5cffacb521432ab2aaf0887b39ad76e c0ca49c9fdab7effb0a6f7a91403f974889734ba84626b00a474eef1fec969ffd644 | |- fw_version: 0x00000001 (1) |- hw_version 0x00000033 (51) |- sd_req: 0x87 |- type: APPLICATION |- sd_size: 0 |- bl_size: 0 |- app_size: 30176 | |- hash_type: SHA256 |- hash: b4767e557c167df5a78f2e1e380b5181879094b1e6819965eb7499e079a8269e | |- is_debug: False

Please suggest me how can i solve it.