OTA（BLE FOTA）

RE: OTA（BLE FOTA）

Menon — Wed, 18 Mar 2026 13:57:39 GMT

Hello,

Thanks for sharing the logs from the mobile application. It does not appear that the issue is related to GATT caching.

Could you also share the RTT/UART logs from the nRF device itself (the device being updated, not the mobile application)? Those logs are necessary to understand what is happening on the device side.

For example, when using the sample I pointed out in my previous response, opening the COM port shows logs from both MCUboot and the application. Please see the screenshot below for reference. I mentioned that sample because, if logging is not currently enabled in your setup, it would be helpful to follow that sample to configure it.

Kind Regards,

Abhijith

RE: OTA（BLE FOTA）

Ryon_pan — Wed, 18 Mar 2026 02:24:07 GMT

Hello,

Thank you for your guidance.

The attached documents record the firmware update details for the first and subsequent reconnections.

Please help analyze where the setting is causing the problem. Why can't the firmware be updated on the first connection, and why does it only work after disconnecting and reconnecting?

devzone.nordicsemi.com/.../first_5F00_conncetion.txt devzone.nordicsemi.com/.../reconnection.txt

RE: OTA（BLE FOTA）

Menon — Tue, 17 Mar 2026 10:06:58 GMT

Hello,

Please refer to this sample exercise where log messages are enabled. You can collect logs using the nRF Logger mobile application from the device manager app. If you are using the nRF Connect mobile application, you can view the logs by sliding the screen (to the right).

Kind Regards,

Abhijith

RE: OTA（BLE FOTA）

Ryon_pan — Tue, 17 Mar 2026 03:34:50 GMT

I'm using the NRF Connect Device Manager app to connect to my device. I'm not sure where to find the logs, but as you can see in the screenshot, the device management information was clearly faulty the first time I connected; it couldn't recognize the bootloader name and bootloader mode.

If I disconnect the BLE connection and then reconnect, the bootloader name and bootloader mode can be recognized, as shown in the image below. What could be the reason that the bootloader name and bootloader mode were not recognized the first time?

RE: OTA（BLE FOTA）

Menon — Fri, 13 Mar 2026 12:57:58 GMT

Hello,

[quote user=""]1. After the update, sometimes some functions of my device are abnormal, while others are normal. A reset is required for all functions to work correctly (this problem doesn't occur every time after an update, it happens occasionally). I would like to know the reason for this.[/quote]

Could you share some more details about this? For example, what exactly is not working after the update?

Do you have any logs that you can share here? It would be helpful to enable the bootloader logs and check whether they provide any information about the issue you are observing.

[quote user=""] After my device is flashed with firmware via J-Link, the first time it connects to the phone and I try to update the firmware using nRF Connect Device Manager, the update fails to start. After a few seconds, the phone displays a "connection timed out" message, requiring me to disconnect. After reconnecting to the phone, the firmware update can begin. It seems that after flashing firmware via J-Link, a connection to the phone is required to complete pairing information exchange before subsequent connections can initiate firmware updates. However, I don't have a pairing function set up in my software. What could be the reason for this?(This problem can be reproduced 100%)[/quote]

Have you also checked the logs from the mobile application? This could potentially be related to the phone-side GATT cache. Based on the description, it does not immediately appear to be an issue related to the DFU/bootloader.

For both issues, it would be helpful to collect logs from the device as well as from the mobile application and share them here.

I would like to point out that MCUboot support for the nRF54L10 in NCS v2.9.1 is in an experimental state. If possible, it is recommended to update to NCS v3.1.0 or later

See the section software maturity categories.

Kind Regards,

Abhijith