Skip to content

Conversation

nandojve
Copy link
Member

@nandojve nandojve commented Aug 22, 2025

The trusted-firmware-m/31755 changes modified profile_definition from 32 to 48 bytes in the platform/ext/common/template/flash_otp_nv_counters_backend.h file.

This change moved fields that are necessary to perform an image upgrade. The issue is visible only when upgrading from an old image (without the changes) to a new one or vice versa. This means that TF-M 2.1.1 do not allow upgrade/downgrade to/from TF-M 2.2.0 or newer versions.

This revert the change to allow migration from Zephyr 3.7.1 LTS to newer images like 4.2.0.

More details from the change can be visualized in: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/31755

depends on https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/42130

The 31755 changes modified profile_definition from 32 to 48 bytes in
the platform/ext/common/template/flash_otp_nv_counters_backend.h file.

This change moved fields that are necessary to perform a an image
upgrade. The issue is visible only when upgrading from an old image
(without the changes) to a new one or vice versa. This means that
TF-M 2.1.1 do not allow upgrade/downgrade to TF-M 2.2.0 or newer.

This revert the change to allow migration from Zephyr 3.7.1 LTS to
newer images like 4.2.0.

More details from the change can be visualized in:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/31755

Signed-off-by: BUDKE Gerson Fernando <[email protected]>
@etienne-lms
Copy link
Contributor

Indeed this change makes sense to have FW update compatible with previous release of immutable BL2. Since recent TF-M moves to this new field size, maybe it would be worth to have a configuration option to allow selecting the older or newer field size.

@nandojve
Copy link
Member Author

nandojve commented Sep 2, 2025

Hi @etienne-lms ,

Indeed this change makes sense to have FW update compatible with previous release of immutable BL2. Since recent TF-M moves to this new field size, maybe it would be worth to have a configuration option to allow selecting the older or newer field size.

I'm waiting the outcome of https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/42130. I recommend someone from ST take a look on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants