Azure FOTA issue: MCUboot does not load new image from secondary slot

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Thu, 20 Jan 2022 07:22:21 GMT

Good morning

Nice to hear that it works, good job!

I will suggest your comment as an Answer. So if you confirm that, future customers who see this post will know it has a solution.

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Thu, 20 Jan 2022 05:49:50 GMT

Good morning, Sigurd!

I tried to program my board using a J-link debugger. It solved my issue!! It seems like newtmgr blocked mcuboot from working properly. Now the new firmware is running after rebooting 🙂

Thank you so much for pointing me in the right directions here! This post is discussing a similar problem as mine, and made me try with the other way of programming the board.

Have a lovely day!

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 12:51:44 GMT

Thank you so much! I will check out the forum in the meantime and let you now if I figure anything out 🙂 Have a nice day!

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Wed, 19 Jan 2022 12:31:00 GMT

It indeed seems strange. Since the board is using MVUBoot, I would think there should always be the image currently running listed, at least.

I will try to replicate this on my nRF9160DK, but this could take some time, so I might not be done until Friday.

In the meantime: Have you checkout out JaredWolff's support forum?
He most likely have better insights into issues specific to this board.

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 11:24:44 GMT

Ah, I understand! Thanks a lot. That makes sense. Hmm, would be great to figure other ways to debug the problem.

newtmgr image listgave me this:

This seems a little strange to me...?

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Wed, 19 Jan 2022 10:28:04 GMT

[quote user="Tonja"]I am not sure if I understood what you mean by this. Could you explain me further? [/quote]

When programming the board, newmgr communicate with mcumgr using the serial interface.
Therefore, the serial interface is reserved for newtmgr, and can not be used for logging.

If you had the cable, you could disable this, and log using the serial interface instead.
However, let us see if we can debug the issue another way first.

I am thinking maybe we can get some information from the newtmgr.
First, I suggest to see if you can get anything useful from:

newtmgr image list

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 10:06:56 GMT

If it is an issue, I can try to get hold of the right programming cable for my connector in order to program the board without using the USB line

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 10:03:33 GMT

Hi,

I am programming the board using newtmgr!

[quote userid="106736" url="~/f/nordic-q-a/83775/azure-fota-issue-mcuboot-does-not-load-new-image-from-secondary-slot/348451#348451"]While I have not confirmed it, I suspect the logging issue is due to the bootloader using the serial interface for programming.
Since you want to program the board using the bootloader, it would be unwise to disable this.[/quote]

I am not sure if I understood what you mean by this. Could you explain me further? :) May the problem be that I am using newtmgr for programming?

Thank you so much for good answers and for looking into my problem

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Wed, 19 Jan 2022 09:58:03 GMT

[quote user="Tonja"]This is my log during reboot. SPM seems to log properly, but I am nit sure if the other logging is from mcuboot? I guess not?[/quote]

Yep, this is the same kind of log as I get when I build for the circuitdojo_feather_nrf9160ns on the nRF9160DK.
There is no MCUBoot log in the one you sent.

While I have not confirmed it, I suspect the logging issue is due to the bootloader using the serial interface for programming.
Since you want to program the board using the bootloader, it would be unwise to disable this.

How do you program your board?

Are you able to use the tools mcumgr or newtmgr?

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 09:07:00 GMT

Just to be sure :)

This is my log during reboot. SPM seems to log properly, but I am nit sure if the other logging is from mcuboot? I guess not?

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
Flash regions           Domain          Permissions
00 03 0x00000 0x20000   Secure          rwxl
04 31 0x20000 0x100000  Non-Secure      rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region             Domain          Permissions
00 07 0x00000 0x10000   Secure          rwxl
08 31 0x10000 0x40000   Non-Secure      rwxl

Peripheral              Domain          Status
00 NRF_P0               Non-Secure      OK
01 NRF_CLOCK            Non-Secure      OK
02 NRF_RTC0             Non-Secure      OK
03 NRF_RTC1             Non-Secure      OK
04 NRF_NVMC             Non-Secure      OK
05 NRF_UARTE1           Non-Secure      OK
06 NRF_UARTE2           Secure          SKIP
07 NRF_TWIM2            Non-Secure      OK
08 NRF_SPIM3            Non-Secure      OK
09 NRF_TIMER0           Non-Secure      OK
10 NRF_TIMER1           Non-Secure      OK
11 NRF_TIMER2           Non-Secure      OK
12 NRF_SAADC            Non-Secure      OK
13 NRF_PWM0             Non-Secure      OK
14 NRF_PWM1             Non-Secure      OK
15 NRF_PWM2             Non-Secure      OK
16 NRF_PWM3             Non-Secure      OK
17 NRF_WDT              Non-Secure      OK
18 NRF_IPC              Non-Secure      OK
19 NRF_VMC              Non-Secure      OK
20 NRF_FPU              Non-Secure      OK
21 NRF_EGU1             Non-Secure      OK
22 NRF_EGU2             Non-Secure      OK
23 NRF_DPPIC            Non-Secure      OK
24 NRF_REGULATORS       Non-Secure      OK
25 NRF_PDM              Non-Secure      OK
26 NRF_I2S              Non-Secure      OK
27 NRF_GPIOTE1          Non-Secure      OK

SPM: NS image at 0x20200
SPM: NS MSP at 0x2001f718
SPM: NS reset vector at 0x26405
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
[00:00:00.202,514] <inf> resani_main: test
[00:00:00.202,575] <inf> watchdog: Watchdog timeout installed. Timeout: 3000
[00:00:00.202,606] <inf> watchdog: Watchdog started
[00:00:00.202,606] <inf> watchdog: Watchdog feed enabled. Timeout: 1500
[00:00:00.202,667] <inf> cloud: Cloud init started
[00:00:00.202,667] <inf> cloud: This may take a while if a modem firmware update                                             is pending
[00:00:00.202,667] <inf> cloud: Modem dfu no error: 0
[00:00:00.202,697] <inf> azure_fota: Current firmware version: 1.0.0
[00:00:00.202,697] <dbg> azure_iot_hub.azure_iot_hub_init: Azure FOTA initialize                                            d
[00:00:00.202,728] <dbg> azure_iot_hub.connection_state_set: New connection stat                                            e: STATE_INIT
[00:00:00.202,728] <wrn> at_notif: Already initialized. Nothing to do
[00:00:00.202,758] <inf> cloud: Successfully initialized and configured AT
[00:00:00.204,376] <inf> cloud: Successfully initialized and configured modem
[00:00:00.304,473] <inf> resani_main: Cloud connect pin low

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 08:55:57 GMT

Hi,

Good idea! However, it seems like the same pins are used...

build/mcuboot/zephyr/zephyr.dts:

build/zephyr/zephyr.dts:

However I am using the following overlay file with another speed. May this introduce any issues?

Thank you so much for your help

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Wed, 19 Jan 2022 08:40:11 GMT

After you build, you can check the mcuboot uart configuration in build/mcuboot/zephyr/zephyr.dts.
Does this use the same pins as the application, build/zephyr/zephyr.dts?

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 08:14:09 GMT

I tried to enable CONFIG_BOOTLOADER_MCUBOOT in the prj.conf file of the Hello World sample. Building the sample with circuitdojo_feather_nrf9160ns and flashing onto the sparkfun thing plus still did not give me any logging from MCUboot. I tried both with and without the changes in bootloader/mcuboot/boot/zephyr/prj.conf.

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 07:45:01 GMT

Hi

Thanks for the reply! :)
I am using sdk version 1.7. Strange... I was not able to run the samples with the nrf9160dk_nrf9160ns boardfile on the Sparkfun thing plus board. The boradfile I am using for my own program is circuitdojo_feather_nrf9160ns. Could this be the issue? Something with the UART configuration?

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Wed, 19 Jan 2022 07:39:02 GMT

[quote user="Tonja"] Instead I am trying to implement the similar functionality in my own project, and it does not seem like the mcuboot logging is enabled.[/quote]

I recommend that you try a minimal sample with the bootloader enabled to see if you are able to enable it.
Add CONFIG_BOOTLOADER_MCUBOOT to zephyr/samples/hello_world, and try to run this on your chip.
With this, you will not be able to interact with the bootloader. However, it should still print logs.

When I add your prj.conf yo the azure_fota sample and run it on a nRF9160DK, I get logs. This also seems to work for me without changes to the bootloader/mcuboot/boot/zephyr/prj.conf.

Which version of the nRF Connect SDK are you using?

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Wed, 19 Jan 2022 06:59:19 GMT

Another detail is btw that I am running my code on a Sparkfun thing plus device with nrf9160 chip. I have tried to enable CONFIG_SERIAL together with the two flags mentioned above, but there is still no logging from MCUboot.. any suggestions?

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Tue, 18 Jan 2022 16:37:04 GMT

I am not running the azure fota sample directly. Instead I am trying to implement the similar functionality in my own project, and it does not seem like the mcuboot logging is enabled. Did I put the config flags in the wrong file maybe?

Best regards
Tonja

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Tue, 18 Jan 2022 15:00:48 GMT

Hi,

When you run the azure_fota sample, can you see the following at the start of your log?

*** Booting Zephyr OS build v2.7.0-ncs1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1  ***

If you can, this means that the bootloader log is working.

Regards,
Sigurd Hellesvik

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Tonja Joseph — Tue, 18 Jan 2022 14:42:36 GMT

Hi,

I added the following two lines to C:\ncs\bootloader\mcuboot\boot\zephyr\prj.conf

CONFIG_MCUBOOT_LOG_LEVEL_DBG=y
CONFIG_MCUBOOT_UTIL_LOG_LEVEL_DBG=y

But no additional logging appears. Do I need to do something more?

RE: Azure FOTA issue: MCUboot does not load new image from secondary slot

Sigurd Hellesvik — Tue, 18 Jan 2022 12:49:06 GMT

Hi Tonja

Maybe there are more information in the MCUBoot logs.

Try to enable them using the method described in this post.

Regards,
Sigurd Hellesvik