DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

Håkon Alseth — Thu, 22 Aug 2024 12:06:57 GMT

Hi,

I see that you have a dedicated thread on your specific issue. I suggest that you continue in that thread.

Kind regards,

Håkon

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

Sankton — Thu, 22 Aug 2024 11:56:24 GMT

Håkon Alseth
HI Hakon
I am facing similar issue as above person

while dfu upgrade thru nrf device app I am getting error -> "error : : NO entry "

SDK 2.3.0
Tool chain 2.4.0

I followed all steps above still no resolution .

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

Håkon Alseth — Fri, 11 Nov 2022 10:09:15 GMT

Great to hear!

Hope you have a wonderful weekend!

Kind regards,

Håkon

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

ayuzva — Thu, 10 Nov 2022 15:41:12 GMT

The second issue seems to have been resolved also after a pristine rebuild of the project directory. Perhaps the application update image had the wrong layout. Thank you.

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

Håkon Alseth — Thu, 10 Nov 2022 14:56:43 GMT

Hi,

[quote user="ayuzva"]

I was able to resolve the issue of not being able to transfer by including pm_static.yml in my project directory.

[/quote]

Great that you found this!

This should be done for all "upgrade project" to align the flash layout as your original mcuboot expects.

[quote user="ayuzva"]I re-opened this ticked because even though I am able to transfer the update images and boot them, I am unable to confirm them. After the transfer is finished and the target has restarted and booted up, nRF Connect Device Manager tries to confirm the image and returns "Device returned error: In Value (3)". This also happens when I try to confirm manually through the "Advanced" interface.[/quote]

To eliminate any firmware related issues, could you try to run the function "ret = boot_write_img_confirmed();" in the init of your updated project?

This will manually verify a "test" firmware, and swap it as a permanent image.

Kind regards,

Håkon

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

ayuzva — Wed, 09 Nov 2022 18:12:02 GMT

Hi Håkon Alseth ,

I was able to resolve the issue of not being able to transfer by including pm_static.yml in my project directory.

I re-opened this ticked because even though I am able to transfer the update images and boot them, I am unable to confirm them. After the transfer is finished and the target has restarted and booted up, nRF Connect Device Manager tries to confirm the image and returns "Device returned error: In Value (3)". This also happens when I try to confirm manually through the "Advanced" interface.

Meanwhile, the logs do not show any issues.

00> [00:00:58.944,274] <inf> mcuboot_util: Swap type: none
00> [00:00:58.948,577] <inf> mcuboot_util: Swap type: none
00> [00:00:59.040,557] <inf> mcuboot_util: Swap type: none
00> [00:00:59.041,381] <inf> mcuboot_util: Swap type: none
00> [00:01:40.856,719] <inf> mcuboot_util: Swap type: none
00> [00:01:40.857,543] <dbg> mcuboot_util: boot_write_magic: writing magic; fa_id=2 off=0xe3ff0 (0xe3ff0)
00> [00:01:40.858,367] <dbg> mcuboot_util: boot_write_swap_info: writing swap_info; fa_id=2 off=0xe3fd8 (0xe3fd8), swap_type=0x2 image_num=0x0
00> [00:01:40.860,626] <inf> mcuboot_util: Swap type: test
00> [00:01:40.864,959] <inf> mcuboot_util: Swap type: test

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

ayuzva — Wed, 09 Nov 2022 15:26:38 GMT

Thank you Håkon Alseth the size has been fixed.

The example that I have used as a starting point is this one:

Add DFU support to your application

With all debugging logging enabled, the only message I am logging is:

<inf> mcuboot_util: Swap type: revert

When I read the image information from nRF Connect Device Manager I only see:

Image 0

Slot: 0
Version 0.0.0
Hash: 0x...
Flags: Bootable, Active

When I was using internal flash only, I saw information about two slots. I believe the second slot is not recognized by the MCUmgr for some reason.

In addition to the above in child_image/mcuboot.conf I do also have:

CONFIG_NCS_MCUBOOT_IN_BUILD=y

While in the prj.conf I have:

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUMGR=y
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y
CONFIG_MCUMGR_SMP_BT=y

CONFIG_FLASH=y
CONFIG_NRFX_QSPI=y
CONFIG_NORDIC_QSPI_NOR=y

CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y
CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=n

CONFIG_MCUMGR_LOG_LEVEL_DBG=y
CONFIG_MCUMGR_IMG_MGMT_LOG_LEVEL_DBG=y
CONFIG_MCUMGR_SMP_LOG_LEVEL_DBG=y
CONFIG_IMG_MANAGER_LOG_LEVEL_DBG=y
CONFIG_BT_DFU_SMP_LOG_LEVEL_DBG=y
CONFIG_FLASH_LOG_LEVEL_DBG=y
CONFIG_IMG_MGMT_VERBOSE_ERR=y

RE: DFU over BLE + MCUboot + External Flash QSPI: "MGMT_ERR_ENOENT"

Håkon Alseth — Wed, 09 Nov 2022 13:19:36 GMT

Hi,

Which example are you using as a starting-point?

[quote user=""]Whenever I try to upload the update image from nRF Connect Device Manager I get "Remote error: No Entry (5)". This is translated from a "MGMT_ERR_ENOENT" error code return from img_mgmt_read_info() of MCUmanager. I have seen this thread with a similar issue:[/quote]

This indicates that you are using an application aware DFU process, ie. that your application is fetching the image and storing it to flash.

This will therefore require that the application has certain configurations enabled as well as the mcuboot child_image.

Do you have a log output from the nRF that you can share?

The size in DT should be provided as bits, and you have set 512MBit (size=<536870912>; -> 64MByte), while the part number that you list:

[quote user=""]AT25QL641[/quote]

indicates that the flash is 64 MBit.

Kind regards,

Håkon