FOTA over Bluetooth Low Energy using the nRF5340 DK

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

Menon — Thu, 17 Jul 2025 11:01:52 GMT

Hello,

I recommend following the steps mentioned in the sample I pointed out in my last reply. I believe it covers most of the configurations. Please give it a try and let me know how it goes.

Kind regards,
Abhijith

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

sasikumar p — Thu, 17 Jul 2025 10:17:58 GMT

Hello Abhijith,

Thank you for the clarification and recommendation.

I completely understand the benefits of switching to the latest SDK. However, since our product is already deployed in the field and built on SDK v2.6.4, migrating to a newer version isn’t feasible at this point.

Given that, I’d appreciate your guidance on how to properly implement FOTA over BLE using MCUmgr with SDK v2.6.4.

Could you please advise on the exact steps or overlays required for SDK v2.6.4 to make BLE DFU work reliably?

Best regards,
Sasikumar

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

Menon — Thu, 17 Jul 2025 10:07:01 GMT

Hello Sasikumar,

If you're about to start your development and can switch to the latest SDK, I highly recommend doing so, as it provides the latest configurations and bug fixes.

However, if you can’t and need to stick with your current SDK version, you can still try the Academy exercise, just make sure to follow the steps that correspond to your SDK version. I noticed that your SDK version doesn't fall exactly under any of the categories mentioned there, but I believe you can follow the steps listed under v2.6.2–v2.5.0.
Also, please refer to this sample.

Kind regards,
Abhijith

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

sasikumar p — Thu, 17 Jul 2025 09:46:16 GMT

Hello,

Thank you for your previous response.

I’m currently working with the nRF5340 DK and SDK version v2.6.4, and I would like to enable FOTA (DFU over BLE) in this version.

Could you please guide me on the correct steps or configurations required to implement FOTA using MCUmgr over BLE with SDK v2.6.4?

Any information about necessary configurations (prj.conf), overlays, partition settings, or compatible samples would be greatly appreciated.

Best regards,
Sasi

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

Menon — Tue, 15 Jul 2025 18:43:35 GMT

Hello,

This issue could be related to the SDK version you are using. Are you building the application using Sysbuild?

To ensure you're using the correct sample from the repository, could you please confirm which branch you're selecting for l9/l9_e5sol? Please refer to the screenshot below. Note that the main branch only works with NCS v3.0.0 and above.

Regarding the configuration, I believe what you're looking for is CONFIG_MCUMGR_TRANSPORT_BT, which is enabled by setting CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU.

Kind Regards,

Abhijith

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

sasikumar p — Tue, 15 Jul 2025 14:12:10 GMT

Hi,

Thank you for the suggestion.

Exercise Used : I9/I9_e5sol
Bluetooth Address: C7:01:13:DD:1E:93
App Used: nRF Connect for Mobile (Android)
Development kit: nRF5340 DK
sdk version : V2.6.4

1. However, I’ve tried this on three different mobile devices (all with the latest version of the nRF Connect for Mobile app), and unfortunately, I don’t see the DFU icon in the top-right corner as shown in your screenshot. I’ve checked both Android and iOS, and made sure Bluetooth and permissions are enabled.

If there's a specific version of the app or a setting that enables the DFU option, I’d appreciate any guidance.

2.I'm working on enabling DFU over BLE using the MCUmgr protocol. As part of the setup,
I'm trying to enable the following configuration in my prj.conf:
CONFIG_MCUMGR_SMP_BT=y
However, I'm unable to add this successfully — it either gets ignored during build or causes configuration errors.
Could you please advise on the correct way to enable this config for my target board (e.g., nrf5340dk_nrf5340_cpuapp)?
Also, are there any dependencies or overlays required for this setting?

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

Menon — Tue, 15 Jul 2025 13:09:08 GMT

Hello,

Sorry for getting back to you a bit late. It's summer vacation here in Norway, which has increased the workload a bit. This caused some delay in getting back to you on this issue.

[quote user="sasikumar p"]nRF Connect for Mobile: Yes, I tried it. Device shows up, and I can connect and browse services, but it doesn't allow file uploads for DFU — hence I moved to Device Manager[/quote]

nRF Connect for Mobile does allow file upload and DFU. See my screenshot below, if you click on the DFU button in the top right corner, it will allow you to choose the file for BLE DFU.

I have tried this sample on my end using the nRF5340DK, and it looks like it's working fine on my side. I used NCS v3.0.2 with the build configuration set to nrf5340dk/nrf5340/cpuapp.

I also tried using the Device Manager app, and I don't see this issue. I'm sharing the logs from my nRF5340DK after a complete DFU and restart. I tested it on Android with Device Manager App version 2.6.0.

Please make sure you are using the correct image for testing, as I noticed a different name in your screenshot (I assume you renamed zephyr.signed.bin).

*** Booting MCUboot v2.1.0-dev-ae1ee57f3906 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
I: Image version: v2.9.0
*** Booting My Application v2.9.0-079365ef40a1 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
Starting Bluetooth Peripheral LBS sample
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF53x (0x0003)
I: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: F4:C7:81:29:60:92 (random)
I: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x218f
Advertising successfully started
Connected
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: perm
*** Booting MCUboot v2.1.0-dev-ae1ee57f3906 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=good, swap_type=0x3, copy_done=0x3, image_ok=0x1
I: Boot source: none
I: Image index: 0, Swap type: perm
I: Starting swap using move algorithm.
I: Bootloader chainload address offset: 0xc000
I: Image version: v2.9.0
*** Booting My Application v2.9.0-079365ef40a1 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
Starting Bluetooth Peripheral LBS sample
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF53x (0x0003)
I: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: F4:C7:81:29:60:92 (random)
I: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x218f
Advertising successfully started
*** Booting MCUboot v2.1.0-dev-ae1ee57f3906 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x3, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
I: Image version: v2.9.0
�*** Booting My Application v2.9.0-079365ef40a1 ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
Starting Bluetooth Peripheral LBS sample
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF53x (0x0003)
I: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: F4:C7:81:29:60:92 (random)
I: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x218f
Advertising successfully started

I recommend trying with a different phone to see if the issue might be device-specific. Also, if you’re using an older version of the mobile app, please try updating it to the latest version. See if restarting the phone makes any difference.

Let me know if the same issue occurs with nRF Connect for Mobile, and check whether there are any errors from the nRF5340DK visible in the logs. If you find anything, please share those logs as well.

Kind Regards,

Abhijith

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

sasikumar p — Mon, 14 Jul 2025 10:22:10 GMT

Hi,
any update on this?

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

sasikumar p — Thu, 10 Jul 2025 10:06:41 GMT

Hi Abhijith,

Thanks for the response. You're right — the screenshot I shared earlier was from the nRF Device Manager app (not nRF Connect for Mobile). Apologies for the confusion.

App used: nRF Device Manager (initially confused with nRF Connect for Mobile).

nRF Connect for Mobile: Yes, I tried it. Device shows up, and I can connect and browse services, but it doesn't allow file uploads for DFU — hence I moved to Device Manager.

Other BLE samples: Yes, I’ve tested some of the basic BLE samples (e.g., Peripheral UART), and they work fine — connections are stable and I can exchange data.

Latest Status Update:

I'm now using the nRF Device Manager app for the DFU process.

The Bluetooth connection is now stable — the device no longer disconnects repeatedly (0x13 error has been resolved).

I can connect and send text data over BLE using the app.

However, when I try to upload a .bin file for FOTA, I get the following error:
Mcu Mgr Error: NOT_SUPPORTED (8)

I have share the mobile log

devzone.nordicsemi.com/.../Log-2025_2D00_07_2D00_10-12_5F00_27_5F00_29.txt

RE: FOTA over Bluetooth Low Energy using the nRF5340 DK

Menon — Tue, 08 Jul 2025 08:05:43 GMT

Hello,

From the screenshots you have shared, it looks like the nRF Device Manager app. Can you confirm which mobile app you are using here?

Have you tried nRF Connect for Mobile? If so, how did it go?
Have you tried any other BLE samples from the SDK? If so, how did they go?

Also, please check the log from the mobile app, it might indicate the reason for the disconnect. Kindly share the log here as well.

Kind regards,
Abhijith