How to do DFU over bluetooth in nRF connect SDK 2.3.0

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Menon — Fri, 27 Oct 2023 05:46:30 GMT

Hello,

Read more about boot swap types. It should work with "test and confirm". Try to provide the swap type from the application itself instead of from the mobile app. See the MCUboot APIs. Include boot_write_image_confirmed and boot_is_image_confimed.

Kind Regards,

Abhijith

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Theja — Fri, 27 Oct 2023 05:28:43 GMT

Hi, it's working with "confirm only" option in nrf connect mobile app.

What's the difference between "test and coinfirm" and "confirm only", What's actually going on internally?

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Menon — Wed, 25 Oct 2023 03:43:50 GMT

Hello,

A bit strange, but is this the whole log? MCUboot is reverting back to the old image here; this can happen if something with the newly installed image is wrong or invalid. Is the same happening with the sample I attached here? Usullay MCUboot will test and then confirm the image, but I couldn't find any logs mentioning this.

Kind Regards,

Abhijith

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Theja — Fri, 20 Oct 2023 07:48:54 GMT

Hello, I tried that one as well, but it didn't work. To be sure you understand the problem, the first time I performed DFU, everything went smoothly. However, the next time I attempted DFU for the same device, the bootloader printing this

[quote userid="126494" url="~/f/nordic-q-a/104513/how-to-do-dfu-over-bluetooth-in-nrf-connect-sdk-2-3-0/451307"]" *** Booting Zephyr OS build v3.2.99-ncs2 ***<CR><LF>
I: Starting bootloader<CR><LF>
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: revert<CR><LF> "[/quote]

and booted the first image (i.e., the image from before the first DFU or the code that had been flashed using J-link),

I tried the confirm only option in the mobile app, but it didn't work out.

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Menon — Fri, 20 Oct 2023 05:45:38 GMT

Hello,

From the very short log you shared, swap type is getting reverted. While doing the OTA DFU, which swap type are you mentioning from the mobile app? You need to mention swap type "test and confirm." Can you also try giving the swap type confirm only from the app and see whether this is working for you or not?

Kind Regards,

Abhijith

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Theja — Thu, 19 Oct 2023 12:42:49 GMT

Hi Menon Thanks for your help, It was a flash partition-related issue, but it is now operational. However, I have a DFU issue. While I performing DFU for the same device a second time, the Bootloader reverts to the first image and Disconnecting.

prints as shown.

" *** Booting Zephyr OS build v3.2.99-ncs2 ***<CR><LF>
I: Starting bootloader<CR><LF>
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: revert<CR><LF> "

what could be the reason behind this?

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Menon — Wed, 11 Oct 2023 12:12:27 GMT

Hello,

[quote user="Theja"]When I dump the code(without DFU), it works fine, but after DFU, the read values are incorrect, so I'm wondering if the bootloader is writing the application to that location after DFU and I'm also unable to perform DFU in succession one after the other.[/quote]

I am not sure whether I understand the issue correctly. What do you mean by reading values here? I recommend you check the partition manager report to get an idea of how the flash is divided. I am attaching a simple sample, which I tested for nrf52833DK, and the partition manager report is as follows:

Is there any log or error message from the device when you try to do DFU repeatedly? I recommend testing the attached sample to see if the same is happening or not.

Please expect some delay after this response, as I will be away for the next two days

.devzone.nordicsemi.com/.../OTA_5F00_dfu_5F00_nrf52833dk.zip

Kind Regards,

Abhijith

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Theja — Tue, 10 Oct 2023 11:33:35 GMT

Hi Menon,

Thanks for the reply, I'm able to do DFU over bluetooth.

However, I have a problem. I'm using a nrf52833 SOC, which has 512 KB of flash memory, and I used 0x00 to 0x50000 of that memory for the bootloader and the application after that I'm using for data storage.

When I dump the code(without DFU), it works fine, but after DFU, the read values are incorrect, so I'm wondering if the bootloader is writing the application to that location after DFU and I'm also unable to perform DFU in succession one after the other.

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

Menon — Tue, 10 Oct 2023 09:05:46 GMT

Hello,

The documents pointed out by @Yohan philippe look good. Please let me know if you are still struggling to find something.

Kind Regards,

Abhijith

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

yohan — Tue, 10 Oct 2023 08:05:32 GMT

And a documented sample: devzone.nordicsemi.com/.../ncs-dfu

RE: How to do DFU over bluetooth in nRF connect SDK 2.3.0

yohan — Tue, 10 Oct 2023 08:00:26 GMT

Hi ! Not sure if it is what you are searching for, but there is common configuration files used to enable BLE OTA in the sample directory:

nrf/samples/common/mcumgr_bt_ota_dfu