OTA（BLE FOTA）

[Ryon_pan]

The MCU is NRF54L10, the SDK is NCS2.9.1, and the firmware is updated using MCUboot update mode.

Configuration as follows：

# sysbuild.conf

SB_CONFIG_BOOTLOADER_MCUBOOT=y

# prj.conf

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

When updating firmware using the nRF Connect Device Manager mobile app, I encountered the following issues:
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.
2. 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%)

[Menon]

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