BLE_DFU BL653dvk Mcumgr error()

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Fri, 03 Jun 2022 11:55:14 GMT

Hi Shikamaru,
Could you answer my last question ?

[quote user="Vinay S"]At least the "NOT_SUPPORTED" error didn't show up ? and you managed to send the image ?[/quote]

Could you check why NOT_SUPPORTED didn't appear ?

Could you explain what you meant by "DFU is not happened which is expected." in your previous reply ?
I really don't know how you tested, you are basically simply saying that "it doesn't work". How you did the FOTA , did the image get through ? have you tried to read the secondary slot ? Have you check if it's copied to the external flash ?

Please try to do as much debugging as possible. We can only give you advice if we have enough information, it's difficult for us to debug without the hardware and the information about what you have added to your application.

You need to step into the code and need to get to understand how the MCUBoot works and how the SMP_SVR works.

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Thu, 02 Jun 2022 13:28:42 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370699#370699"]Could you try doing with CONFIRM only ? [/quote]

Yes, i have tried . No luck .

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370699#370699"]I would suggest to test my example with UART on a DK first before moving to your app. [/quote]

agreed, am able to build it successfully , however I don't have relative board to test that and one more thing in your example you are using qspi , here i have to use SPI .

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370699#370699"]At least the "NOT_SUPPORTED" error didn't show up ? and you managed to send the image ? [/quote]

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Thu, 02 Jun 2022 12:48:06 GMT

Could you try doing with CONFIRM only ?
I would suggest to test my example with UART on a DK first before moving to your app.

At least the "NOT_SUPPORTED" error didn't show up ? and you managed to send the image ? Could you check what make the NOT_SUPPORTED disappear, from what I can see in the modifications you sent me it's almost the same like in my example.

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Thu, 02 Jun 2022 09:18:14 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370605#370605"]Please describe what exactly you did for testing [/quote]

first I flashed board with one build along with changes of my board added and then i built it again by adding printf just to confirm , took that update.bin file and sent it to board through BLE.

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370605#370605"]Did you test my example alone or you tested by integrating to your app ? [/quote]

I tested it by integrating my changes.

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370605#370605"]How did you do DFU ? Via UART or via BLE ? [/quote]

Via BLE, UART I can't , Both UART we are utilizing for other purpose. So it has to be over BLE only.

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370605#370605"]If you did via BLE did you select CONFIRM instead of TEST & CONFIRM ? [/quote]

No ,I selected TEST and CONFIRM.

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Thu, 02 Jun 2022 08:01:33 GMT

Please describe what exactly you did for testing ? Did you test my example alone or you tested by integrating to your app ?
How did you do DFU ? Via UART or via BLE ?

If you did via BLE did you select CONFIRM instead of TEST & CONFIRM ?

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Thu, 02 Jun 2022 07:02:58 GMT

[quote userid="106945" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370477#370477"]yes i will try that example and i will update here .[/quote]

Hi Hung Bui,

I am able to build your file and i have checked my modified files .I am able to build it and after flashing to the board, the DFU is not happened which is expected. here is the logs.

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Starting Bluetooth Peripheral LBS example
build time: Jun  1 2022 17:58:18

I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: SoftDevice Controller build revision:
I: 0e e7 c5 66 67 18 3c ac |...fg.<.
I: b3 d2 cc 81 a3 dc f1 c0 |........
I: c0 36 02 22             |.6."
I: No ID address. App must call settings_load()
Bluetooth initialized
Advertising successfully started
Connected

I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Starting Bluetooth Peripheral LBS example
build time: Jun  1 2022 17:58:18

I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: SoftDevice Controller build revision:
I: 0e e7 c5 66 67 18 3c ac |...fg.<.
I: b3 d2 cc 81 a3 dc f1 c0 |........
I: c0 36 02 22             |.6."
I: No ID address. App must call settings_load()
Bluetooth initialized
Advertising successfully started
Connected
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Starting Bluetooth Peripheral LBS example
build time: Jun  1 2022 17:58:18


I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: SoftDevice Controller build revision:
I: 0e e7 c5 66 67 18 3c ac |...fg.<.
I: b3 d2 cc 81 a3 dc f1 c0 |........
I: c0 36 02 22             |.6."
I: No ID address. App must call settings_load()
Bluetooth initialized
Advertising successfully started
Connected

I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test
I: Swap type: test

In app also , it will say validating and after that ,it will disconnect immediately and board went for reset. Can you help me to figure this out

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Wed, 01 Jun 2022 13:53:48 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370448#370448"]What you provided look good but could you check you have the overlay in both the application and the MCUBoot child image ? [/quote]

Yes , i have checked it , overlay file is there in both folder.

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370448#370448"]I have made an example here to use the mx25r64 as the external flash for MCUBoot and it worked for me. My suggestion is to try modify my example to see if you can make it work for the is25 ? [/quote]

yes i will try that example and i will update here .

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370448#370448"]Do you see any error log on the nRF52 ? [/quote]

Till now , no

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Wed, 01 Jun 2022 12:39:39 GMT

Hi Shikamaru,
What you provided look good but could you check you have the overlay in both the application and the MCUBoot child image ?
I have made an example here to use the mx25r64 as the external flash for MCUBoot and it worked for me. My suggestion is to try modify my example to see if you can make it work for the is25 ?

Do you see any error log on the nRF52 ?

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Wed, 01 Jun 2022 09:27:59 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370377#370377"]Yes, then please let us know what's the modification you made to change it from internal flash to external flash.
Please don't point to another case because there are lots of modification and different samples there. [/quote]

attached one pm_static.yml file for external flash modification . here it is.

external_flash:
  address: 0x00000
  end_address: 0x80000
  region: external_flash
  size: 0x80000

mcuboot_secondary:
  address: 0x00000
  device: IS25
  end_address: 0x39000
  region: external_flash
  size: 0x39000

in prj.conf file configured the spi to communicate with external flash . here it is.

# Ensure an MCUboot-compatible binary is generated.
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="DFU_LE"

# Enable the LBS service
CONFIG_BT_LBS=y
CONFIG_BT_LBS_POLL_BUTTON=y
CONFIG_DK_LIBRARY=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048


CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_LOG=y

CONFIG_GPIO=y

# CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

CONFIG_NORDIC_QSPI_NOR=n

CONFIG_FLASH=y
CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_SPI_NRFX_RAM_BUFFER_SIZE=32 

# Enable mcumgr.
CONFIG_MCUMGR=y

# Enable most core commands.
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

# Allow for large Bluetooth data packets.
CONFIG_BT_L2CAP_TX_MTU=252
CONFIG_BT_BUF_ACL_RX_SIZE=256

# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n


#CONFIG_BLR_BOARD_INIT=y
# CONFIG_MCUBOOT_INDICATION_LED = y

# CONFIG_MULTITHREADING=y
# CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0
# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

Mcuboot's prj.conf file

#
# Copyright (c) 2021 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# In order to provide board specific configurations to the MCUboot child image
# we also need to provide a base configuration for MCUboot. This file contains
# the basic configurations needed to successfully build and run MCUboot.
CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0
# MCUboot requires a large stack size, otherwise an MPU fault will occur
CONFIG_MAIN_STACK_SIZE=10240

#CONFIG_DEBUG_OPTIMIZATIONS=y

# Enable flash operations
CONFIG_FLASH=y

# This must be increased to accommodate the bigger images.
CONFIG_BOOT_MAX_IMG_SECTORS=128

CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y # former CONFIG_MODE_MINIMAL
### Ensure Zephyr logging changes don't use more resources
CONFIG_LOG_DEFAULT_LEVEL=0
### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y
CONFIG_CBPRINTF_NANO=y

CONFIG_NORDIC_QSPI_NOR=n

CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096

# If you don't add this when setting CONFIG_SPI=y, you'll get a lot of undefined references from the nrfx spim driver
# E.G. "undefined reference to `z_impl_k_sleep'"
CONFIG_MULTITHREADING=y

In overlay file also enabled the is25 external flash as below:

/ {
	chosen {
		nordic,pm-ext-flash = &is25;
	};
};

&spi1 {
	compatible = "nordic,nrf-spim";
	label = "SPI_1";
	status = "okay";
	sck-pin = <41>;
	mosi-pin = <40>;
	miso-pin = <4>;

	cs-gpios = <&gpio0 23 GPIO_ACTIVE_LOW>;

	is25: is25@0 {
		compatible = "jedec,spi-nor";
		status = "okay";
		label = "IS25";
		spi-max-frequency = <8000000>;
		reg = <0>;
		jedec-id = [ 9d 40 13  ];
		size = <4194304>;   ///check with yogeshh

		sfdp-bfp = [
		   e5 20 fb ff  ff ff ff 3f  44 eb 08 6b  08 3b 04 bb
		   fe ff ff ff  ff ff 00 ff  ff ff 44 eb  0c 20 0f 52
		   10 d8 00 ff  d6 49 c5 00  82 df 04 e3  44 03 67 38
		   30 b0 30 b0  f7 bd d5 5c  4a 9e 29 ff  f0 50 f9 85
		];
	};
};

These are the modification did for external flash .

Regards,

Shikamaru

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Wed, 01 Jun 2022 09:17:14 GMT

Yes, then please let us know what's the modification you made to change it from internal flash to external flash.
Please don't point to another case because there are lots of modification and different samples there.

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Wed, 01 Jun 2022 05:55:45 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370254#370254"]So you saying that it works fine when you follow the link ? But not when you try to do it with external flash ? [/quote]

Yes i din't see that msg while working with internal flash

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Tue, 31 May 2022 13:52:41 GMT

I can't help you if you don't give enough information.

So you saying that it works fine when you follow the link ? But not when you try to do it with external flash ?

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Tue, 31 May 2022 13:13:43 GMT

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370180#370180"]

Please list the step you did.

Did you manage to do FOTA without external flash ?

[/quote]

As i mentioned above , i followed the same link and am able to do that. and the link which you have shared is same as mine. both are same link

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Tue, 31 May 2022 11:22:03 GMT

Hi Shikamaru,

Please list the step you did.

Did you manage to do FOTA without external flash ?

RE: BLE_DFU BL653dvk Mcumgr error()

Shikamaru — Tue, 31 May 2022 10:07:48 GMT

Hi ,

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370140#370140"]Have you tried to test doing FOTA with internal flash ?[/quote]

Yes am able to complete that.

[quote userid="2121" url="~/f/nordic-q-a/88443/ble_dfu-bl653dvk-mcumgr-error/370140#370140"]Please let us know how you implement the MCUMGR, SMP_SVR in your application.[/quote]

for this am following below link

( https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu#ble_testing )

regards,

Shikamaru

RE: BLE_DFU BL653dvk Mcumgr error()

Hung Bui — Tue, 31 May 2022 08:45:46 GMT

Hi Shikamaru,

Please let us know how you implement the MCUMGR, SMP_SVR in your application.

Have you tried to test doing FOTA with internal flash ? Please go through this blog if you haven't: https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu

Please check if you get any log on the nRF52 side.