[McuMgr] Error: IN_VALUE (3) during DFU update by SMP service

RE: [McuMgr] Error: IN_VALUE (3) during DFU update by SMP service

AHaug — Mon, 09 Oct 2023 07:34:00 GMT

Glad to hear you were able to resolve it!

Getting a hand of how DFU on the dual core nRF5340 works can be tricky, so please feel free to open new tickets if you have any other issues or questions

Kind regards,
Andreas

RE: [McuMgr] Error: IN_VALUE (3) during DFU update by SMP service

Julien — Fri, 06 Oct 2023 14:26:42 GMT

Hi AHaug,

I tried with the repo of Hellesvik and it works well.

I think it come from nrf53840 and the dual core, i need to develop more in order to understand why.

Thanks for the support,

Julien

RE: [McuMgr] Error: IN_VALUE (3) during DFU update by SMP service

AHaug — Thu, 05 Oct 2023 14:32:08 GMT

Hi,

As this guide is quite old (tested for NCS v1.8.0), I'm curious if you do see the same things when following the steps in from relevant samples in this repository https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples? For instance using the mcuboot_smp_ble sample in https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/smp

Let me know if you're able to cross examine what could be the difference or not and I will continue looking into it from my end as well

Kind regards,
Andreas

RE: [McuMgr] Error: IN_VALUE (3) during DFU update by SMP service

Julien — Thu, 05 Oct 2023 08:29:06 GMT

Is what i got from uart log when failed

Starting Bluetooth Peripheral LTS example
E: Unable to register handle 0x0016
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF53x (0x0003)
I: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: C5:9C:33:25:14:38 (random)
I: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x2077
Advertising successfully started
Connected
I: Swap type: none
I: Swap type: none
I: Swap type: none
I: Swap type: none
I: Swap type: none

and when successful

Starting Bluetooth Peripheral LBS example
E: Unable to register handle 0x0016
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF53x (0x0003)
I: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: C5:9C:33:25:14:38 (random)
I: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x2077
Advertising successfully started
Connected
I: Swap type: none
I: Swap type: none
I: Swap type: none
I: Swap type: test
I: Swap type: test
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Starting Bluetooth Peripheral LBS example
E: Unable to register handle 0x0016
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 224.11902 Build 2231721665
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: C5:9C:33:25:14:38 (random)
I: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x2077
Advertising successfully started
Connected
I: Swap type: perm
I: Swap type: perm

It seems the mistake come from Swap type : test is missing.