Seeking DFU-OTA Example for nRF5340 with Latest SDK

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Fri, 16 Aug 2024 11:18:29 GMT

Hello,

I tested this using your prj.conf file but was unable to reproduce the issue on my end. I integrated your entire prj.conf into my test application for OTA DFU and attempted the DFU with the generated image to a device. However, I did not experience the delay that your logs indicate.

Could you clarify how you're measuring this delay of over 1 minute? I am attaching the log of my DFU process; none of the timestamps show a time difference of over 1 minute.

I've attached the generated build/.config file. Please review it and let me know if I missed any important configurations.

devzone.nordicsemi.com/.../build_5F00_config.zip

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Bluetooth Peripheral LBS example
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: D9:76:44:D8:3F:05 (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: 1, Swap type: none
E: Failed to open flash area ID 1: -2
I: Image index: 0, Swap type: none
I: Image index: 1, Swap type: none
E: Failed to open flash area ID 1: -2
I: Image index: 1, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 1, Swap type: perm
E: Failed to open flash area ID 1: -2
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: perm
I: Image index: 1, Swap type: perm
E: Failed to open flash area ID 1: -2
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Bluetooth Peripheral LBS example
 [00:00:00.006,805] <inf> fs_nvs: 2 Sectors of 4096 bytes
 [00:00:00.006,835] <inf> fs_nvs: alloc wra: 0, fe8
 [00:00:00.006,835] <inf> fs_nvs: data wra: 0, 0
 [00:00:00.037,811] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
 [00:00:00.037,841] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
 [00:00:00.037,872] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
 [00:00:00.040,283] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
 [00:00:00.042,755] <inf> bt_hci_core: Identity: D9:76:44:D8:3F:05 (random)
 [00:00:00.042,785] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
 [00:00:00.042,785] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
Advertising successfully started
Connected
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Bluetooth Peripheral LBS example
 [00:00:00.006,622] <inf> fs_nvs: 2 Sectors of 4096 bytes
 [00:00:00.006,622] <inf> fs_nvs: alloc wra: 0, fd0
 [00:00:00.006,622] <inf> fs_nvs: data wra: 0, 1c
 [00:00:00.037,841] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
 [00:00:00.037,872] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
 [00:00:00.037,902] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
 [00:00:00.040,313] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
 [00:00:00.042,816] <inf> bt_hci_core: Identity: D9:76:44:D8:3F:05 (random)
 [00:00:00.042,846] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
 [00:00:00.042,877] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
Advertising successfully started
Connected

Kind regards,
Abhijith

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Krishnachandran_a — Mon, 12 Aug 2024 04:03:31 GMT

Hi,

Thanks for the update.

We tested both methods, that you suggested, but nothing positive. prj.conf is attached. please have a look.

CONFIG_MAIN_STACK_SIZE= 10240

#for LOG
CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_RUNTIME_FILTERING=y
CONFIG_LOG_BUFFER_SIZE=10240
CONFIG_LOG_PRINTK=y
CONFIG_LOG_PROCESS_TRIGGER_THRESHOLD=0
CONFIG_LOG_TAG_MAX_LEN=8

#for timer
CONFIG_NRFX_TIMER0=y

#for events
CONFIG_EVENTS=y

#for fuel gauge
CONFIG_FUEL_GAUGE=y

#for I2C
CONFIG_I2C=y

#for dmic
CONFIG_AUDIO=y
CONFIG_AUDIO_DMIC=y
CONFIG_DMA=y

#for NVS
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

#for RTC
CONFIG_NRFX_RTC0=y

#To enable floating point values
CONFIG_FPU=y

#for SPI
CONFIG_SPI=y
CONFIG_NRFX_SPIM2=y
CONFIG_NRFX_SPIM4=y

#for Bluetooth
CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=n
CONFIG_BT_SMP=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_BAS=y
CONFIG_BT_DIS=y
CONFIG_BT_DIS_PNP=n
CONFIG_BT_DEVICE_NAME="test"
CONFIG_BT_DIS_MODEL="test"
CONFIG_BT_DIS_MANUF="test"
CONFIG_BT_DIS_HW_REV=y
CONFIG_BT_DIS_HW_REV_STR="0.1.1"
CONFIG_BT_DIS_SW_REV=y
CONFIG_BT_DIS_SW_REV_STR="0.0.1"
CONFIG_BT_DIS_FW_REV=y
CONFIG_BT_DIS_FW_REV_STR="0.0.1.1"
#GATT_CLIENT needed for requesting ATT_MTU update
CONFIG_BT_GATT_CLIENT=y
#PHY update needed for updating PHY request
CONFIG_BT_USER_PHY_UPDATE=y
#For data length update
CONFIG_BT_USER_DATA_LEN_UPDATE=y
#Over-ride various BT settings for extended data packet size
CONFIG_BT_ATT_PREPARE_COUNT=4
CONFIG_BT_L2CAP_TX_MTU=498
CONFIG_BT_L2CAP_TX_FRAG_COUNT=15
CONFIG_BT_BUF_EVT_RX_SIZE=251
CONFIG_BT_BUF_CMD_TX_SIZE=251
CONFIG_BT_BUF_ACL_RX_SIZE=502
CONFIG_BT_BUF_ACL_TX_COUNT=15
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_RX_STACK_SIZE=4096
CONFIG_BT_DEVICE_APPEARANCE=833

#for UART
CONFIG_UART_INTERRUPT_DRIVEN=n
CONFIG_UART_ASYNC_API=y
CONFIG_UART_3_ASYNC=y
CONFIG_UART_USE_RUNTIME_CONFIGURE=y

#for Warchdog
CONFIG_WATCHDOG=y
CONFIG_WDT_DISABLE_AT_BOOT=n

#for OTA 
CONFIG_NCS_SAMPLES_DEFAULTS=y
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP=y
CONFIG_NRF53_UPGRADE_NETWORK_CORE=y
CONFIG_UPDATEABLE_IMAGE_NUMBER=2
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2304


#for ota callback
CONFIG_MCUMGR_MGMT_NOTIFICATION_HOOKS=y
CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS=y

CONFIG_PCD_APP=y

Thanks in advance.

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Tue, 06 Aug 2024 08:12:40 GMT

Hello,

I'm not sure why this is happening. I suspect it might be because of the connection parameters you are using in the application. For testing, try doing a DFU to a device running the OTA sample (where the firmware image is your custom application and the device is running the OTA sample) and vice versa (a device running your firmware and the new image to update is the OTA sample).

If that also doesn't work, please share a minimal project or minimal prj.config. I will try to test it here.

Kind regards,

Abhijith

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Maya. — Fri, 02 Aug 2024 04:30:44 GMT

Hi,

We have checked the thread, the issue is not exactly the same. that is we didn't observe any stuck during the OTA, but observer slowness in OTA process, also observer several unexpected restart after OTA.

Regards,

Maya

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Thu, 01 Aug 2024 15:51:51 GMT

Hello,

Have you checked the thread I pointed out in my last response? Is your issue similar to what is described there?

Kind regards,

Abhijith

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Maya. — Wed, 31 Jul 2024 07:19:05 GMT

Hi Abhijith.

Thanks for the update.

[quote userid="115767" url="~/f/nordic-q-a/113070/seeking-dfu-ota-example-for-nrf5340-with-latest-sdk/496094"]Is this issue occurring with the sample application provided in the Developer Academy, or does it happen when you configure the application according to your needs?[/quote]

This is happening in custom application, in Example, OTA is happening in a good time, we thought that is because of less code size. and we opt same configurations for our app.

[quote userid="115767" url="~/f/nordic-q-a/113070/seeking-dfu-ota-example-for-nrf5340-with-latest-sdk/496094"] which mobile application are you using to achieve DFU OTA?[/quote]

nRF Connect.

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Mon, 29 Jul 2024 20:02:21 GMT

Hello,

Is this issue occurring with the sample application provided in the Developer Academy, or does it happen when you configure the application according to your needs? Also, which mobile application are you using to achieve DFU OTA? I am investigating a similar issue in another ticket—please take a look at this thread. Let me know if your issue is related or very similar.

Kind regards,

Abhijith

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Maya. — Fri, 26 Jul 2024 10:14:02 GMT

Hi,

[quote userid="115767" url="~/f/nordic-q-a/113070/seeking-dfu-ota-example-for-nrf5340-with-latest-sdk/494990"]Could you try including the config CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP? [/quote]

After including this we get same result .. that is OTA is happening in same time ( Approxmatly 1 Minute 10 Sec)

Both Screenshots are attached.

with CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP

with out CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP

Also you can observe couple of restart after OTA in both logs.

Thanks in advance

Maya

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Mon, 22 Jul 2024 09:30:21 GMT

Hello,

Glad to hear that you succeeded in doing OTA DFU. Could you try including the config CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP? This will speed up the OTA DFU to some extent. I'm not sure if I fully understand your mention of the restart—does the device restart unpredictably? I recommend that you share the log to provide more insight into this behavior.

Kind Regards,

Abhijith

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Maya. — Fri, 19 Jul 2024 05:07:50 GMT

Hello Abhijith,

The issue has been resolved, and we can now proceed with OTA DFU without any further issues. However, we've observed a slowness in OTA compared to previous updates, along with a couple of extra device restarts post-OTA. Could you please advise if this behavior is expected?

Best regards, Maya

RE: Seeking DFU-OTA Example for nRF5340 with Latest SDK

Menon — Tue, 16 Jul 2024 09:36:48 GMT

Hello Maya,

You can explore our Developer Academy course that covers Device Firmware Update (DFU) and bootloaders. Detailed explanations of OTA DFU are provided there, along with complete code and solutions available in the corresponding GitHub repository for the course. I hope this information will be helpful for you. If you are still facing issues, I recommend sharing the complete logs, especially describing the error messages encountered during OTA DFU.

Kind Regards,

Abhijith