Updating an nRF52 application over the air with OTA DFU

RE: Updating an nRF52 application over the air with OTA DFU

Bjørn Kvaale — Thu, 28 Jun 2018 07:43:59 GMT

If you are using softdevice v6, most likely the issue is that you are using the wrong --sd-req code. The blog shows you two ways how to check that you are using the correct --sd-req code: either use the command:

nrfutil pkg generate --help

or if the softdevice is not found there, program the softdevice & use the programmer app in nrf connect. You can find the correct softdevice ID there.

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Tue, 26 Jun 2018 15:02:19 GMT

Thanks a lot for your reply.

1. I've followed the blog post step by step.

2.The ble_app_hrs project runs properly.

3. I haven't been seeing process of DFU showing percentage.

4. I've used the same --sd-req 0x98 as in the blog post and not 0x00a8!!!

5. I need to check if I have a logging information.

My DK was burned out, so I'm waiting for new board.

BR,

Ran

RE: Updating an nRF52 application over the air with OTA DFU

Bjørn Kvaale — Tue, 26 Jun 2018 09:14:20 GMT

Did you follow the blog post I linked to step by step? Did you test the ble_app_hrs project by erasing the dev kit, only flashing the softdevice & the application to the dev kit first & see if that works?

From what you are explaining, it seems that the DFU failed to complete since the device is advertising as "DFuTarg" instead of "Nordic_HRM". This is most likely why the device goes back into bootloader mode instead of advertising "Nordic_HRM".

Do you have any logging information that you could upload? Does the DFU complete to 100% in nrf connect?

Which --sd-req code are you using for the softdevice when you create the zip package using nrfutil in Step C2 of the blog post? If you are using s132 v6 softdevice, it should be 0x00a8. You can also use the command: nrfutil pkg generate --help

or load the softdevice to your dev kit & check the softdevice code using nrf go studio or nrf programmer app in nrf connect for pc.

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Sun, 24 Jun 2018 07:16:47 GMT

Hello Bjorn,

I was trying to insert a video with no success (MP4 ~100MB). If you can give me an E-mail address to send the video it will be great.

I've tested with Galaxy S8, Model:SM-G950F, Android version 8.0.0.

After selecting the ZIP file of ble_app_hrs project, the following messages were populated:

1. Starting DFU.

2. Starting bootloading.

3. Connecting

When it stopped, I disconnected from device, and pressed SCAN.

I thought I should recognize the device as HRS service but the device was recognized as DfuTarg.

Do I have a misunderstanding with the DFU process or something is not working properly here?

Best regards.

RE: Updating an nRF52 application over the air with OTA DFU

Bjørn Kvaale — Fri, 22 Jun 2018 10:01:25 GMT

As I mentioned previously, do you have another phone to test the DFU with? That way, we can check to make sure you have done all of the steps correctly. If the DFU works with the other phone, then we know that you have done all of the dfu steps correctly & that there could be an issue with your phone. Then, we can continue looking at the issue then.

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Thu, 21 Jun 2018 13:54:26 GMT

hello Bjorn,

I had a mistake, my phone is Xiaomi, Redmi Note 4, Android 7.0 NRD90M, MIUI version: MIUI Global 9.2 (9.2.1.0 NCFMIEK).

RE: Updating an nRF52 application over the air with OTA DFU

Bjørn Kvaale — Thu, 21 Jun 2018 12:54:57 GMT

Is the Huawei a P9 or a P9 lite? We have noticed some issues regarding these phones, so do you by any chance have another phone to test the DFU with? That way, we can check if a small mistake was made when you followed the blog post or whether it is the phone that is causing the issues.

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Wed, 20 Jun 2018 12:56:53 GMT

Hello Bjorn,

The post is great, I've done all steps successfully - up to step D3.

In step D3 I got the same results as reported above:

With nRF Connect when selecting the ZIP file - nothing happens.

With nRF Toolbox when pressing 'Select device' and 'SCAN' - returns error "Permission denied".

What's wrong?

Snapshots of nRF Toolbox:

1. The device is recognized correctly:

2. The ZIP file selected correctly:

3. Can't select device nor SCAN- "Permission denied":

EDIT: BTW, the nRF Toolbox version is 2.6.0 and in DFU\About I found this:

Does it not supporting nRF52832 and S132?!

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Wed, 20 Jun 2018 11:16:00 GMT

Thank a lot for your reply.

I'll follow the blog post.

My phone is HUAWEI, Android 7.0 NRD90M.

RE: Updating an nRF52 application over the air with OTA DFU

Bjørn Kvaale — Wed, 20 Jun 2018 11:01:33 GMT

Have you taken a look at this excellent blog post? If you follow all of the steps carefully, the DFU should work out of the box. What kind of a phone are you testing this with? Which Android version are you using?

RE: Updating an nRF52 application over the air with OTA DFU

Ran Ratson Kohavi — Tue, 19 Jun 2018 14:14:41 GMT

Well, I've installed nRF Toolbox and now I can select the file, but when choosing 'Select device' and pressing 'SCAN' it returns error "Permission denied".

Any help with this will be gratefully accepted.