Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

RE: Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

Vidar Berg — Wed, 06 Mar 2024 11:02:12 GMT

Which "entry method" do you use to enter serial recovery mode (https://github.com/nrfconnect/sdk-mcuboot/blob/323fb663e832d4c45eb2fc2d30a3955684791b7d/boot/zephyr/Kconfig.serial_recovery#L133)?

Note: If you select the bootloader child image for debugging, only the bootloader will be programmed onto the device while the merged.hex file contains all the firmware images. The bootloader will boot the application on boot unless there is something that signals the bootloader to enter serial recovery mode instead.

RE: Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

thanosPr — Wed, 06 Mar 2024 10:46:58 GMT

Let me describe my issue again.

I have successfully added and completed dfu using mcuboot in serial recovery mode on nrf52840.

My issue is on getting into mcuboot serial recovery mode by programming the target with merged.hex file.

I realised that when i am writing the target with merged.hex file (zephyr build system), the target is not getting into mcuboot serial recovery mode. However, this issue is gone when i am uploading the file using debugging option on VS Code.

RE: Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

Vidar Berg — Wed, 06 Mar 2024 10:36:41 GMT

[quote user="thanosPr"]I uploaded my bin file using debug option from VS Code and i compare it with the merged.hex that is produced giving to me different result.[/quote]

Can you please elaborate on what the difference is?

[quote user="thanosPr"]Could you please help me why using debugging option my nrf52 is getting into mcuboot serial recovery mode (using the corresponding pin) instead of programming it with merged.hex ?[/quote]

Sorry, I'm not quite sure what you mean. Could you please post some images to illustrate the problem?

[quote user="thanosPr"]Let me attach a picture below:[/quote]

I'm not sure what to look for in this picture.

RE: Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

thanosPr — Wed, 06 Mar 2024 09:21:04 GMT

Maybe there was a misunderstanding.

I uploaded my bin file using debug option from VS Code and i compare it with the merged.hex that is produced giving to me different result.

Could you please help me why using debugging option my nrf52 is getting into mcuboot serial recovery mode (using the corresponding pin) instead of programming it with merged.hex ?

Let me attach a picture below:

RE: Flashing firmware bin using NRF programmer included the DFU Fota using mcuboot serial recovery mode

Vidar Berg — Tue, 27 Feb 2024 12:00:45 GMT

Hello,

[quote user=""]I faced up with an issue while i was setting up the production process.[/quote]

Initial programming of the device must be performed through the debug interface using an external programmer, as the chip is shipped blank from our factory. There is no pre-programmed bootloader to handle flashing through a USB or UART.

[quote user=""]Since the target was programmed using merged.hex, i realised that the microcontroller did not get into mcuboot serial recovery mode.[/quote]

There are different methods you can enable in your MCUBoot build to make the bootloader enter serial recovery on startup as you can see from the configuration options here: https://github.com/nrfconnect/sdk-mcuboot/blob/cb64eca4df86554a8da61e23d8fe4469257ff8be/boot/zephyr/Kconfig.serial_recovery#L133

[quote user=""]May i have to make any special setting in nrf programmer to load succesfully mcuboot serial recovery mode or the uploaded file is different one than merged file?[/quote]

To perform serial recovery, you currently need to use the mcumgr-client tool: https://docs.zephyrproject.org/latest/services/device_mgmt/mcumgr.html

Best regards,

Vidar