mcuboot: Image in the secondary slot is not valid!

[Jeffery]

Hi Nordic team

Last week and before, I tried sdk connect v3.0.0 http_application_update example.

Everything was fine. Pressed button1 to download new bin file and then reseted DK to swap the slot.

LED1 and LED2 turned on to show version 2. Used the original host name and file name at this example.

the prj.conf and main.c were not modified.

However, this week, I tested same code and same DK again. It still can download file from host. But, swapping got failed.

Log showed "<err> mcuboot: Image in the secondary slot is not valid!". Then, back to first slot and ran the old application.

Do you have any idea about this error?

    

[Simon]

It seems like this is triggering, because this is evaluated to true. Could you do some debugging and check the following:

• In boot_is_header_valid()
  • Does this happen?
  • Does this happen?
  • Does this happen?
• In boot_image_check()
  • Does this happen?
  • Does this happen?
  • Does this happen?

When you figure out, please tell me and I will investigate further

Best regards,

Simon

[Jeffery]

Hi Simon

At mcuboot loader.c, I added log messages at the six points as you mentioned to figure out the error reason.

pic1: I added "@@@ number" at loader.c

pic2: After my DK downloaded the binary file and rebooted by RESET button, the log showed "@@@ 6".

         So, it got error from bootutil_img_validate().

pic3: I tried to mark off bootutil_img_validate(). Then, tried FOTA again. It can work. Downloaded and swapped both

         worked.

I guessed the app_update.bin file was updated and changed at your AWS bucket these days.

Two weeks ago, I tested FOTA  by sdk ncs 1.3.0 http_application_update. It worked without this error.