Flash area error while doing DFU using nRF Connect

[Krishnachandran_a]

Dear support team,

I am getting an error while performing DFU using nRF Connect.

[00:02:39.702,697] <inf> mcuboot_util: Swap type: none
[00:02:39.702,972] <err> mcumgr_img_grp: Failed to open flash area ID 1: -2

My SDK version is 2.4.2, I need to do DFU using BLE simultaneously, for that i tried to modify Example mcuboot_smp_ble_simultaneous , but without modifying anything, while performing DFU by compiling this code i am getting this error, Even after getting this error new imaged is flashed successfully after DFU. i don't know the reason. my complete serial log is attached bellow. 

D: RDSR 40 QE 1 need 1: no-change
I: Starting bootloader
I: Swap type: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
*** Booting Zephyr OS build 28a3fca7da5c ***
Change this to see it change.
[00:00:00.030,853] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,883] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.030,914] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
[00:00:00.032,623] <inf> bt_hci_core: Identity: C5:DB:0C:FE:67:B3 (random)
[00:00:00.032,653] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
[00:00:00.032,653] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2077
Bluetooth initialized
Advertising successfully started
[00:02:39.702,697] <inf> mcuboot_util: Swap type: none
[00:02:39.702,972] <err> mcumgr_img_grp: Failed to open flash area ID 1: -2
[00:02:39.978,576] <inf> mcuboot_util: Swap type: none
D: RDSR 40 QE 1 need 1: no-change
I: Starting bootloader
I: Swap type: perm
I: Swap type: perm
I: Image upgrade secondary slot -> primary slot
I: Erasing the primary slot
I: Copying the secondary slot to the primary slot: 0x1af50 bytes
D: writing magic; fa_id=4 off=0xf3ff0 (0xffff0)
D: erasing secondary header
D: erasing secondary trailer
I: Image upgrade secondary slot -> primary slot
I: Erasing the primary slot
I: Copying the secondary slot to the primary slot: 0x2e8d4 bytes
D: writing magic; fa_id=1 off=0x3fff0 (0x3fff0)
I: Turned on network core
I: Turned off network core
D: erasing secondary header
D: erasing secondary trailer
I: Bootloader chainload address offset: 0xc000
ÿ*** Booting Zephyr OS build 28a3fca7da5c ***
Krishnachandran_Test....
[00:00:00.030,883] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,914] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.030,944] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
[00:00:00.032,653] <inf> bt_hci_core: Identity: C5:DB:0C:FE:67:B3 (random)
[00:00:00.032,684] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
[00:00:00.032,684] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2077
Bluetooth initialized
Advertising successfully started

If any idea regarding this, please help. Thanks in advance.

[Sigurd Hellesvik]

Hi,

Which target board do you build for?

Regards,
Sigurd Hellesvik

[Krishnachandran_a]

nRf5340

[KjellArne Amina]

Hi Sigurd,
Good of you to confirm our suspicions. As we said, the DFU works so it does not block our progress. However, it is generating some support requests for our product, when customers and testers think that there is an issue with the firmware update.

We would appreciate a ticket to remove the incorrect error message in a future nrf connect sdk release

Best regrards
Kjell Arne

[Sigurd Hellesvik]

KjellArne Amina said:

We would appreciate a ticket to remove the incorrect error message in a future nrf connect sdk release

I have now created an internal ticket.

[Krishnachandran_a]

is there any solution to exclude these workaround from code.?

[Sigurd Hellesvik]

Nothing yet, no

[AlejandroM]

This is still an issue in SDK 2.9.0, when you try to do an mcumgr image list or upload any FW, but it does not affect it's functionality.

It is worth mentioning, that in some smaller firmware adding the flash_sim.overlay for the application with low memory consumption gets rid of the message, but in applications that consume more RAM, the message still appears:

GW [15:40:55.824,859] <inf> [mcumgr smp] mcuboot_util: Image index: 0, Swap type: none
GW [15:40:55.825,195] <inf> [mcumgr smp] mcuboot_util: Image index: 1, Swap type: none
GW [15:40:55.825,195] <err> [mcumgr smp] mcumgr_img_grp: Failed to open flash area ID 3: -2
GW [17:16:41.167,358] <inf> [mcumgr smp] mcuboot_util: Image index: 1, Swap type: none
GW [17:16:43.895,568] <inf> [mcumgr smp] mcumgr_img_grp: Erased 0x36000 bytes of image slot
GW [17:16:43.986,389] <inf> [mcumgr smp] mcumgr_img_grp: Erased 0x1000 bytes of image slot trailer

The rest of the update works fine for both App and Net Core, but the error is off-putting.

And even trying to build bigger consumption memory application won't build and fail with:

c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `noinit' will not fit in region `RAM'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `RAM' overflowed by 84764 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.