NRF91 SLM FOTA from NCS 1.9.1 to NCS 2.0.0 failing

RE: NRF91 SLM FOTA from NCS 1.9.1 to NCS 2.0.0 failing

AHaug — Thu, 14 Jul 2022 09:33:01 GMT

Hi,

Noted, then we will consider this as resolved from a tech support view as well.

Regarding information about an update of the repo, you will need to contact your local Regional Sales Manager for more information about future plans and road maps for feature/development of the SDK unless the information is publically available on our web pages. Send me a PM if you need the RSMs contact information and I'll send it to you.

Kind regards,
Andreas

RE: NRF91 SLM FOTA from NCS 1.9.1 to NCS 2.0.0 failing

Konstantin Klitenik — Tue, 12 Jul 2022 18:10:17 GMT

Thanks, AHaug. We made a decision to just create a static partition table to keep the address offset the same. From our point of view, we can consider this resolved. But I imagine (and hope) we're not the only ones using SLM so you may want to have some sort of update to the repo.

RE: NRF91 SLM FOTA from NCS 1.9.1 to NCS 2.0.0 failing

AHaug — Tue, 12 Jul 2022 14:00:59 GMT

Hi again,

I've verified the things from above and have a suggestion for you to try:

The default size of MCUBOOT is 48KB on both v1.9.1 and v.2.0.0
The change from v1.9.1 to v2.0.0 is the replacement of SPM (64KB) to TF-M minimal (48KB). This makes start offset of application different
- On V1.9.1 the application start address is 0x20200
- On V2.0.0 the application start address is 0x1c200

This is what causes the application to revert back to the original image.

You can try to enable CONFIG_TFM_CMAKE_BUILD_TYPE_DEBUG=y to make TF-M size 64KB. This should make the start addresses the same.

Let me know if this works out,

Kind regards,
Andreas

RE: NRF91 SLM FOTA from NCS 1.9.1 to NCS 2.0.0 failing

AHaug — Tue, 12 Jul 2022 12:22:41 GMT

Hi,

There has been a change in MCUBOOT from NCS v1.x.x to NCS v2.0.0 including reduction of the mcuboot partition such that v2.0.0 firmware expects that the new image is placed at a different address than in v1.9.1 and the other way around. This leads to firmware upgrade and/or downgrade (v2.0.0 -> 1.x.x) not beeing succesful.

I will check around if there are any simple workarounds to make this work.

Ps: I see that my statement about the version changes are not documented on the infocenter pages for MCUboot yet, so I will ask the developers about this aswell.

Kind regards,
Andreas