Android OTA issue

RE: Android OTA issue

Einar Thorsrud — Tue, 02 Jan 2024 08:12:07 GMT

Hi,

You can refer to the SMP Server Sample. Please make a new thread if you have any follow-up questions.

RE: Android OTA issue

binartech — Thu, 28 Dec 2023 16:27:46 GMT

Sorry for the intromission here, but its the only relatively new comment Im finding on the OTA DFU for sdk 2.5.x , any guidance for an OTA DFU on how to add BT OTA DFU to an application using sdk 2.5.0 ? I found one that works for 2.2, .23 requires modifications and doesn't work for 2.5, thanks for any comments

RE: Android OTA issue

Einar Thorsrud — Wed, 20 Dec 2023 15:17:37 GMT

Hi Ethan,

We have tested with setting CONFIG_MCUMGR_GRP_OS_MCUMGR_PARAMS=n in nRF Connect SDK 2.5.0, but are still able to update from an Android device using the smp server sample.

Which SDK version are you using, and are you able to reproduce this with a sample by setting CONFIG_OS_MGMT_MCUMGR_PARAMS=n or CONFIG_MCUMGR_GRP_OS_MCUMGR_PARAMS=n (depending on version)? If not the problem is probably something else (and we would be interested in logs from both the nRF and Android device to try to understand more about what is happening).

Einar

RE: Android OTA issue

EthanZhao — Tue, 19 Dec 2023 01:30:31 GMT

Hi Einar,

Thanks for your replay! But our product has already been released. We need to update our product firmware. However, the OTA flow has been tested only on iOS, not on Android. Here is my config setting. With these settings, when an Android device attempts to perform an OTA update using the device manager, it gets stuck after connecting via then eventually times out. Are there alternative methods for OTA updates from Android devices?

CONFIG_GPIO=y
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_SMP=y
CONFIG_BT_SIGNING=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_ATT_PREPARE_COUNT=5
CONFIG_BT_DEVICE_APPEARANCE=833
CONFIG_BT_DEVICE_NAME_DYNAMIC=y
CONFIG_BT_DEVICE_NAME_MAX=65

CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

CONFIG_I2C=y

# Enable nordic security backend and PSA APIs
CONFIG_NRF_SECURITY=y
CONFIG_MBEDTLS_PSA_CRYPTO_C=y

CONFIG_MBEDTLS_ENABLE_HEAP=y
CONFIG_MBEDTLS_HEAP_SIZE=8192
CONFIG_PSA_CRYPTO_DRIVER_OBERON=n
CONFIG_PSA_CRYPTO_DRIVER_CC3XX=y

#
CONFIG_HEAP_MEM_POOL_SIZE=4096
CONFIG_MAIN_STACK_SIZE=8192


#Enable mcumgr
CONFIG_MCUMGR=y

#Enable most core commands
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y

#Ensure on MCUboot-compatible binary is generated
CONFIG_BOOTLOADER_MCUBOOT=y

#Allow for large Bluetooth data packets
CONFIG_BT_L2CAP_TX_MTU=1024
CONFIG_BT_BUF_ACL_RX_SIZE=512
CONFIG_BT_BUF_ACL_TX_SIZE=251


#Enable the Bluetooth and shell mcumgr transports
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n



#
CONFIG_PRINTK=y
CONFIG_SHELL=y
CONFIG_LOG=y
CONFIG_DEVICE_SHELL=y
CONFIG_POSIX_CLOCK=y

CONFIG_DK_LIBRARY=y

# Power manager
CONFIG_PM=y
CONFIG_PM_DEVICE=y

CONFIG_UART_CONSOLE=n
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y

CONFIG_HWINFO=y

Ethan

RE: Android OTA issue

Einar Thorsrud — Mon, 18 Dec 2023 13:01:30 GMT

Hi Ethan,

I do not see a paticular reason CONFIG_OS_MGMT_MCUMGR_PARAMS (which has chnaged name to MCUMGR_GRP_OS_MCUMGR_PARAMS) should be needed for Android in principle. However, if the Android application (or other SMP client) use the MCUMGR Parameters retrieval command, then it makes sense that it fails if you buil't the nRF application without it. And similarily, if the iOS (or other) implementation does not use it, then it does not matter if it is present or not. By default, we set CONFIG_MCUMGR_GRP_OS_MCUMGR_PARAMS=y in our Bluetooth samples and I suggest you also include it.

Einar