Skip to content

manifest: update tf-m-tests to 2.1.2 #2786

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Apr 24, 2025

Conversation

tomi-font
Copy link
Contributor

@tomi-font tomi-font commented Apr 17, 2025

Pull in the commits needed to update the tf-m-tests revision to the 2.1.2 version.

@NordicBuilder
Copy link
Contributor

NordicBuilder commented Apr 17, 2025

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
tf-m-tests zephyrproject-rtos/tf-m-tests@502ea90 zephyrproject-rtos/tf-m-tests@c712761 (main) zephyrproject-rtos/[email protected]
trusted-firmware-m zephyrproject-rtos/trusted-firmware-m@fa020a8 zephyrproject-rtos/trusted-firmware-m@e2288c1 (main) zephyrproject-rtos/[email protected]

Additional metadata changed:

Name URL Submodules West cmds module.yml
trusted-firmware-m

DNM label due to: 1 project with metadata changes

Note: This message is automatically posted and updated by the Manifest GitHub Action.

wearyzen and others added 7 commits April 24, 2025 09:51
What is changed?
 - Use the updated TF-M that is compatible with the Zephyr's
   latest Ethos-U driver repo.
 - Change the default behavior of TF-M builds to use Ethos driver
   locally fetched by Zephyr, using west update, instead of
   downloading it from external repo.

Why is this change required?
 - This is to be inline with Zephyr's rules to not fetch code from
   external repo.

Fixes #81656

Signed-off-by: Sudan Landge <[email protected]>
(cherry picked from commit 9b0623e)
Updates the https://github.com/zephyrproject-rtos/trusted-firmware-m/
to fix the build error on stm32u5 due to gcc revision

Signed-off-by: Francois Ramu <[email protected]>
(cherry picked from commit 676c3d2)
Only set CMAKE_INSTALL_MESSAGE in a single location, remove the
unconditional overrides of the value in other locations.

This prevents dozens of rather pointless messages appearing in the build
log when CONFIG_TFM_BUILD_LOG_QUIET is set.
```
Installing: /home/jordan/code/workspace/build/nrf5340dk/...
```

Signed-off-by: Jordan Yates <[email protected]>
(cherry picked from commit b74b092)
…rry-picks

Update brings in flash_area_get_sector.

Signed-off-by: Dominik Ermel <[email protected]>
(cherry picked from commit 789e3f3)
Update west

Signed-off-by: Georgios Vasilakis <[email protected]>
(cherry picked from commit d8b87d6)
Brings some commits from the upstream TF-M which introduce
nRF54L10 ns support.

Signed-off-by: Georgios Vasilakis <[email protected]>
(cherry picked from commit 2717473)
Update TF-M to 2.1.2 from version 2.1.1.

Signed-off-by: Tomi Fontanilles <[email protected]>
(cherry picked from commit dfd0dd0)
@tomi-font tomi-font force-pushed the tf-m-tests_update_2.1.2 branch from 6b8b8ee to 80868ee Compare April 24, 2025 06:52
@tomi-font tomi-font changed the title [nrf noup] manifest: update tf-m-tests to 2.1.2 manifest: update tf-m-tests to 2.1.2 Apr 24, 2025
@rlubos rlubos merged commit 532da2e into nrfconnect:main Apr 24, 2025
27 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants