mcuboot: Image in the secondary slot is not valid!

RE: mcuboot: Image in the secondary slot is not valid!

Simon — Mon, 20 Sep 2021 09:12:52 GMT

ballen7: Could you create a new ticket?

RE: mcuboot: Image in the secondary slot is not valid!

ballen7 — Tue, 14 Sep 2021 00:16:26 GMT

Any progress?

RE: mcuboot: Image in the secondary slot is not valid!

Simon — Fri, 23 Oct 2020 14:18:37 GMT

Jeffery said:

So, FOTA is not considered to be downward compatible?

FOTA should be backwards compatible, just make sure to use static partitions in your new application and place everything in the same location as your old application. In order to achieve this, take the file <old-application>/<build-folder>/partitions.yml, and copy it to <new-application>/pm_static.yml.

Regarding the http_application_update sample not working with NCS v1.3.0, I will report this internally. However, you should still be able to upload your own images to a bucket by following Specifying the image file, Setting up and AWS S3 bucket and Hosting your image on an AWS S3 Server. Could you test this and see if you can make that work?

Best regards,

Simon

RE: mcuboot: Image in the secondary slot is not valid!

Simon — Fri, 23 Oct 2020 14:17:33 GMT

It seems like the image in http://nrfconnectsdk.s3.eu-central-1.amazonaws.com/app_update.bin is intended to be used for the http_application_updates sample on the master branch. I will do some more testing and confirm this.

Best regards,

Simon

RE: mcuboot: Image in the secondary slot is not valid!

Jeffery — Thu, 22 Oct 2020 01:22:46 GMT

Hi Simon

So, FOTA is not considered to be downward compatible?

Like my case, I developed application code on the basis of ncs v3.0.0.

If I upgraded my application code to ncs v3.1.0 and uploaded the app_update.bin to AWS,

as I did DFU, mcuboot (v3.0.0) would reject to swap the new application code.

Right?

RE: mcuboot: Image in the secondary slot is not valid!

Simon — Wed, 21 Oct 2020 14:06:02 GMT

[deleted]

RE: mcuboot: Image in the secondary slot is not valid!

Jeffery — Tue, 20 Oct 2020 07:32:41 GMT

I updated SDK to v3.1.0 and modem to v1.2.1.

Fot http_application_ipdate, same error happened when downloading bin file and reset to swap slot.

FYI.

Jeff

RE: mcuboot: Image in the secondary slot is not valid!

Jeffery — Tue, 20 Oct 2020 06:49:50 GMT

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.

RE: mcuboot: Image in the secondary slot is not valid!

Jeffery — Fri, 16 Oct 2020 06:41:28 GMT

Hi Simon

I will check what you mentioned.

Since this error was weird, did you change your "app_update.bin" file

at "nrfconnectsdk.s3.eu-central-1.amazonaws.com"?

Thanks

RE: mcuboot: Image in the secondary slot is not valid!

Simon — Thu, 15 Oct 2020 12:53:10 GMT

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